Merge pull request #3427 from travis-ci/Heading-Update-v2

Heading update v2

Author: stan-travis

user/deployment-v2/conditional.md

@@ -21,7 +21,7 @@ If *all* conditions specified in the `on` section are met, your build will deplo
 
 The following conditions are available:
 
-### Repo
+## Repo
 
 To deploy only when the build occurs on a particular repository, add `repo` in the form `owner_name/repo_name`:
 
@@ -34,7 +34,7 @@ deploy:
 ```
 {: data-file=".travis.yml"}
 
-### Branch
+## Branch
 
 By default, deployments will only happen on the `master` branch. You can overwrite this by using the `branch` and `all_branches` options.
 
@@ -60,7 +60,7 @@ deploy:
 ```
 {: data-file=".travis.yml"}
 
-### Condition
+## Condition
 
 You can specify a single Bash `condition` that needs to evaluate to `true` in
 order for the deployment to happen.
@@ -78,7 +78,7 @@ deploy:
 ```
 {: data-file=".travis.yml"}
 
-### Tag
+## Tag
 
 You can specify whether or not to deploy on tag builds using the option `tags`.
 If set to to `true` the deployment will only happen on tag builds, if set to
@@ -104,7 +104,7 @@ build when it was initiated.
 Setting `tags` to `true` causes the `branch` condition to be ignored, otherwise
 `$TRAVIS_TAG` is ignored, and the `branch` condition is considered.
 
-### Examples for conditional deployments
+## Examples for conditional deployments
 
 This deploys using a custom script `deploy.sh`, only for builds on the branches
 `staging` and `production`.

user/deployment-v2/custom.md

@@ -10,7 +10,7 @@ machine by adding a custom [`after_success`](/user/customizing-the-build/) step.
 You may choose the [Script provider](/user/deployment/script/) instead, as it
 provides conditional deployment.
 
-### SFTP
+## SFTP
 
 ```yaml
 env:
@@ -33,7 +33,7 @@ The env variables `SFTP_USER` and `SFTP_PASSWORD` can also be
 See [curl(1)](http://curl.haxx.se/docs/manpage.html) for more details on how to
 use cURL as an SFTP client.
 
-### ⋮
+## ⋮
 
 This should also work with services you can deploy to via git.
 

user/deployment-v2/providers/azure-web-apps.md

@@ -10,7 +10,7 @@ after a successful build.
 
 {% include deploy/providers/azure_web_apps.md %}
 
-## Fetching Deployment Progress and Logs
+## Fetch Deployment Progress and Logs
 
 The Azure Web App provider can print Azure's deployment progress to your Travis
 log using the `verbose` option.
@@ -26,7 +26,7 @@ deploy:
 ```
 {: data-file=".travis.yml"}
 
-## Note on .gitignore
+## The .gitignore method
 
 As this deployment strategy relies on Git, be mindful that the deployment will
 honor `.gitignore`.
@@ -35,12 +35,12 @@ If your `.gitignore` file matches something that your build creates, use
 [`before_deploy`](#running-commands-before-and-after-deploy) to change
 its content.
 
-## Deploying to slots
+## Deploy to slots
 
 You might need to deploy multiple branches to different slots. You can set
 multiple providers to deploy to specific slots. The following configuration
 would deploy the `master` branch to the `myapp-staging` slot and the `develop`
-branch to the `myapp-develop` slot. In order to use slots you'll need to [set
+branch to the `myapp-develop` slot. In order to use slots, you'll need to [set
 up staging environments for web apps in Azure App
 Service](https://azure.microsoft.com/en-us/documentation/articles/web-sites-staged-publishing/).
 

user/deployment-v2/providers/bintray.md

@@ -10,7 +10,7 @@ after a successful build.
 
 {% include deploy/providers/bintray.md %}
 
-## Descriptor file
+## Descriptor File
 
 The descriptor is in JSON file format in three sections:
 
@@ -66,12 +66,12 @@ The descriptor is in JSON file format in three sections:
 
 ### Package Section
 
-Bintray package information. The following information is mandatory on open source projects:
+Bintray package information. The following information is mandatory for open-source projects:
 
-- `name` is the Bintray package name
-- `repo` is the Bintray repository name
-- `subject` is the Bintray subject, which is either a user or an organization
-- `vcs_url` is the Bintray version control system url, such as a github repository url
+- `name` is the Bintray package name.
+- `repo` is the Bintray repository name.
+- `subject` is the Bintray subject, which is either a user or an organization.
+- `vcs_url` is the Bintray version control system URL, such as a GitHub repository URL.
 - `licenses` is the [Bintray licences](https://bintray.com/docs/api/#_licenses){: data-proofer-ignore=""}, which is a list with at least one item.
 
 ### Version Section
@@ -80,7 +80,7 @@ Package version information. In case the version already exists on Bintray, only
 
 ### Files Section
 
-Configure the files you would like to upload to Bintray and their upload path.
+Configure the files you want to upload to Bintray and their upload path.
 
 You can define one or more groups of patterns. Each group contains three patterns:
 
@@ -132,7 +132,7 @@ matrixParams as part of the files closure as shown in the following example:
 ]
 ```
 
-### Overwriting Existing Files
+### Overwrite Existing Files
 
 If an artifact by a given name already exists in the Bintray repository, then
 by default it is not overwritten. If you want to replace the existing file,

user/deployment-v2/providers/boxfuse.md

@@ -30,9 +30,9 @@ Finally you can also configure Boxfuse by placing a `boxfuse.conf` file in the
 root of your repository. More info about configuration in the
 [Boxfuse Command-line Client documentation](https://boxfuse.com/docs/commandline/).
 
-### Specifying the app and image version
+### Specify the App and image version
 
-By default Boxfuse will detect the app and the version automatically from the
+By default, Boxfuse will detect the app and the version automatically from the
 name of your payload file.
 
 You can override this using the following:
@@ -49,9 +49,9 @@ You can also use Travis CI [environment variables](/user/environment-variables/)
 like `TRAVIS_BUILD_NUMBER` to assign a version to the image, e.g.
 `image: "myapp:$TRAVIS_BUILD_NUMBER"`.
 
-### Specifying the environment
+### Specify the Environment
 
-By default Boxfuse will deploy to your `test` environment.
+By default, Boxfuse will deploy to your `test` environment.
 
 You can override this using the following:
 
@@ -63,7 +63,7 @@ deploy:
 ```
 {: data-file=".travis.yml"}
 
-### Specifying a configuration file
+### Specify a configuration file
 
 You can also fully configure Boxfuse by placing a `boxfuse.conf` file in the
 root of your repository. You can specify an alternative configuration file like
@@ -77,7 +77,7 @@ deploy:
 ```
 {: data-file=".travis.yml"}
 
-### Specifying custom arguments
+### Specify custom arguments
 
 If the [Boxfuse Client](https://boxfuse.com/docs/commandline) functionality you
 need is not included here, you can pass additional arguments to the Boxfuse
@@ -90,7 +90,7 @@ deploy:
 ```
 {: data-file=".travis.yml"}
 
-### Further information
+### Further Information
 
 Go to the [Boxfuse website](https://boxfuse.com) to learn more about Boxfuse
 and how to configure it.

user/deployment-v2/providers/cloudfiles.md

@@ -9,7 +9,7 @@ Travis CI can automatically upload your build to [Rackspace Cloud Files](https:/
 
 {% include deploy/providers/cloudfiles.md %}
 
-## Specifying files to upload
+## Specify Upload Files
 
 Often, you don't want to upload your entire project to Cloud Files.
 
@@ -35,7 +35,7 @@ deploy:
 ```
 {: data-file=".travis.yml"}
 
-## Deploying to multiple regions or containers:
+## Deploy to multiple regions or containers
 
 If you want to upload to multiple regions or containers, you can do this:
 

user/deployment-v2/providers/codedeploy.md

@@ -57,7 +57,7 @@ of your application is inferred from the file extension of `key` set in your
 If your `.travis.yml` contains both, and they do not match, set `bundle_type`
 explicitly to the correct value.
 
-## Specifying the AWS region
+## Specify the AWS region
 
 You can explicitly specify the AWS region to deploy to with the `region` option:
 

user/deployment-v2/providers/datica.md

@@ -8,7 +8,7 @@ provider: datica
 Travis CI can automatically deploy to [Datica](https://datica.com) after
 a successful build.
 
-In order to setup a deployment you need to:
+In order to set up a deployment, you need to:
 
 ### Find your Git remote
 
@@ -61,7 +61,7 @@ before_deploy: echo "[git.catalyzeapps.com]:2222 ecdsa-sha2-nistp256 BBBB12abZmK
 ```
 {: data-file=".travis.yml"}
 
-### Specifying a directory to deploy
+### Specify a directory to deploy
 
 To only deploy the `build` directory, for example, set `path`:
 

user/deployment-v2/providers/elasticbeanstalk.md

@@ -10,11 +10,11 @@ after a successful build.
 
 {% include deploy/providers/elasticbeanstalk.md %}
 
-## Creating an application without deploying it
+## Create an Application without deploying it
 
 To create an application without deploying it, simply exclude the `env` option and this will only upload the app version without deploying it to a new environment. 
 
-## Controlling which files are included in the ZIP archive
+## Control which files to include in the ZIP archive
 
 You can control which files are included in the ZIP archive you upload with
 `.ebignore` and `.gitignore`, as described in the [AWS CLI documentation](https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/eb-cli3-configuration.html).

user/deployment-v2/providers/engineyard.md

@@ -13,7 +13,7 @@ Travis CI can automatically deploy your [Engine Yard](https://www.engineyard.com
 
 {% include deploy/providers/engineyard.md content=content %}
 
-### Application or Environment to deploy
+## Application or Environment to deploy
 
 By default, the application name will be inferred from your repository name.
 
@@ -27,7 +27,7 @@ deploy:
 ```
 {: data-file=".travis.yml"}
 
-### Deploying branches to different apps or environments
+## Deploy branches to different apps or environments
 
 In order to choose apps or environments based on the current branch use
 separate deploy configurations:
@@ -64,7 +64,7 @@ deploy:
 ```
 {: data-file=".travis.yml"}
 
-### Running migrations
+## Run migrations
 
 You can trigger migrations by using the migrate option: