tweaks

Author: svenfuchs

user/conditional-builds-stages-jobs.md

@@ -7,9 +7,9 @@ You can filter out and reject builds, stages and jobs by specifying conditions i
 
 ## Conditional Builds
 
-Configure Travis CI to only run builds when certain conditions are met. Any builds that do not meet these conditions are listed in the *Requests* tab of your repository, even though the actual build is not generated.
+You can configure Travis CI to only run builds when certain conditions are met. Any builds that do not meet these conditions are listed in the *Requests* tab of your repository, even though the actual build is not generated.
 
-For example, this allows builds only to run on the master branch:
+For example, this allows builds only to run on the `master` branch:
 
 ```yaml
 # require the branch name to be master (note for PRs this is the base branch name)
@@ -21,9 +21,7 @@ Build requests that do not match the condition will not generate a build, but wi
 
 ## Conditional Stages
 
-Configure Travis CI to only include stages when certain conditions are met. Stages that do not match the given condition are silently skipped.
-
-For example, this allows the deploy stage to run only on the master branch:
+You can configure Travis CI to only include stages when certain conditions are met. Stages that do not match the given condition are silently skipped. For example, this allows the deploy stage to run only on the `master` branch:
 
 ```yaml
 stages:
@@ -37,9 +35,7 @@ Stages that do not match the condition will be skipped silently.
 
 ## Conditional Jobs
 
-Configure Travis CI to only include jobs when certain conditions are met.
-
-For example, this includes the listed job only to builds on the master branch:
+You can configure Travis CI to only include jobs when certain conditions are met. For example, this includes the listed job only to builds on the `master` branch:
 
 ```yaml
 jobs:
@@ -50,15 +46,13 @@ jobs:
 ```
 {: data-file=".travis.yml"}
 
-Jobs need to be listed explicitly, i.e., using `jobs.include` (or its alias `matrix.include`), in order to specify conditions for them. Jobs created via [matrix expansion](/user/customizing-the-build/#build-matrix) currently cannot have conditions, but they can be conditionally excluded (see the next section).
+Jobs need to be listed explicitly, i.e., using `jobs.include` (or its alias `matrix.include`), in order to specify conditions for them. Jobs created via [matrix expansion](/user/customizing-the-build/#build-matrix) currently cannot have conditions, but they can be conditionally excluded (see [below](/#conditionally-excluding-jobs)).
 
 Jobs that do not match the condition will be skipped silently.
 
 ## Conditionally Excluding Jobs
 
-Configure Travis CI to exclude jobs only when certain conditions are met.
-
-For example, this will create two jobs on all branches, but only one job (with the env var `ONE=one`) on the master branch:
+You can configure Travis CI to exclude jobs when certain conditions are met. For example, this will create two jobs on all branches, but only one job (with the env var `ONE=one`) on the `master` branch:
 
 ```yaml
 env:
@@ -73,9 +67,7 @@ jobs:
 
 ## Conditionally Allowing Jobs To Fail
 
-Configure Travis CI to allow jobs to fail only when certain conditions are met.
-
-For example, this will allow the job with the env var `TWO=two` to fail when the build runs on the branch `dev`:
+You can configure Travis CI to allow jobs to fail only when certain conditions are met. For example, this will allow the job with the env var `TWO=two` to fail when the build runs on the branch `dev`:
 
 ```yaml
 env: