Updates formatting in README

README.md

@@ -148,13 +148,13 @@ This command will build your project and deploy *Only the necessary files* to yo
 
 The person deploying can select at what point in the git repository they want to check for files that have changed. They can specify a tag, branch or commit hash, or “all” to deploy all files. This is done in the terminal window, in response to a prompt that is surfaced by the tool. If no answer is provided to the prompt, then the deployment script will check for files from the latest version tag (e.g. v1.0.1). If no version tag is found in the repo then it’ll check for files changed since the current branch was branched off of develop (or if the current branch is develop, branched off of master).
 
-##### Common usecases encountered when using  ```brrl -deploy```
+## Common usecases encountered when using  ```brrl -deploy```
 
-**Deploying file changes made on a feature branch.**
+##### Deploying file changes made on a feature branch.
 
 In this case, the deploying user should write "develop" in response to the console prompt. By putting in "develop", all files that have changed since the feature branch diverged from the `develop` branch will be deployed. This works when the targetted Shopify theme is up to date with the files on `develop`. If not, "all" can be written after the prompt instead to deploy all theme files.
 
-**Updating a theme to the latest version.**
+##### Updating a theme to the latest version.
 
 In this case, the deploying user should write the last tag name, e.g. "v1.0.2" in response to the console prompt. This is effective if the deploying user is deploying version `v1.0.3` to a theme that is already up to date with `v1.0.2`. By putting in "v1.0.3", the deployment task finds all files that have changed between versions and deploys only those files.