docs: grammar edits, sentence-case secondary headings

Also changes some heading levels so only one primary
heading appears per page.

1 files changed, 10 insertions, 10 deletions

diff --git a/docs/Bottles.md b/docs/Bottles.md
index 2752ebe03..983fbc537 100644
--- a/docs/Bottles.md
+++ b/docs/Bottles.md
@@ -3,9 +3,9 @@
 Bottles are produced by installing a formula with `brew install --build-bottle $FORMULA` and then bottling it with `brew bottle $FORMULA`. This outputs the bottle DSL which should be inserted into the formula file.
 
 ## Usage
-If a bottle is available and usable it will be downloaded and poured automatically when you `brew install <formula>`. If you wish to disable this you can do it by specifying `--build-from-source`.
+If a bottle is available and usable it will be downloaded and poured automatically when you `brew install <formula>`. If you wish to disable this you can do so by specifying `--build-from-source`.
 
-Bottles will not be used if the user requests it (see above), if the formula requests it (with `pour_bottle?`), if any options are specified on installation (bottles are all compiled with default options), if the bottle is not up to date (e.g. lacking a checksum) or the bottle's `cellar` is not `:any` or equal to the current `HOMEBREW_CELLAR`.
+Bottles will not be used if the user requests it (see above), if the formula requests it (with `pour_bottle?`), if any options are specified during installation (bottles are all compiled with default options), if the bottle is not up to date (e.g. lacking a checksum) or if the bottle's `cellar` is not `:any` nor equal to the current `HOMEBREW_CELLAR`.
 
 ## Creation
 Bottles are created using the [Brew Test Bot](Brew-Test-Bot.md). This happens mostly when people submit pull requests to Homebrew and the `bottle do` block is updated by maintainers when they `brew pull --bottle` the contents of a pull request. For the Homebrew organisations' taps they are uploaded to and downloaded from [Bintray](https://bintray.com/homebrew).
@@ -13,7 +13,7 @@ Bottles are created using the [Brew Test Bot](Brew-Test-Bot.md). This happens mo
 By default, bottles will be built for the oldest CPU supported by the OS/architecture you're building for. (That's Core 2 for 64-bit OSs, Core for 32-bit.) This ensures that bottles are compatible with all computers you might distribute them to. If you *really* want your bottles to be optimized for something else, you can pass the `--bottle-arch=` option to build for another architecture - for example, `brew install foo --bottle-arch=penryn`. Just remember that if you build for a newer architecture some of your users might get binaries they can't run and that would be sad!
 
 ## Format
-Bottles are simple gzipped tarballs of compiled binaries. Any metadata is stored in a formula's bottle DSL and in the bottle filename (i.e. MacOS version, revision).
+Bottles are simple gzipped tarballs of compiled binaries. Any metadata is stored in a formula's bottle DSL and in the bottle filename (i.e. macOS version, revision).
 
 ## Bottle DSL (Domain Specific Language)
 Bottles have a DSL to be used in formulae which is contained in the `bottle do ... end` block.
@@ -48,25 +48,25 @@ By default this is omitted and the Homebrew default bottle URL root is used. Thi
 
 ### Cellar (`cellar`)
 Optionally contains the value of `HOMEBREW_CELLAR` in which the bottles were built.
-Most compiled software contains references to its compiled location so cannot be simply relocated anywhere on disk. If this value is `:any` or `:any_skip_relocation` this means that the bottle can be safely installed in any Cellar as it did not contain any references to its installation Cellar. This can be omitted if a bottle is compiled (as all default Homebrew ones are) for the default `HOMEBREW_CELLAR` of `/usr/local/Cellar`
+Most compiled software contains references to its compiled location so cannot be simply relocated anywhere on disk. If this value is `:any` or `:any_skip_relocation` this means that the bottle can be safely installed in any Cellar as it did not contain any references to its installation Cellar. This can be omitted if a bottle is compiled (as all default Homebrew ones are) for the default `HOMEBREW_CELLAR` of `/usr/local/Cellar`.
 
 ### Prefix (`prefix`)
 Optionally contains the value of `HOMEBREW_PREFIX` in which the bottles were built.
-See description of `cellar`. When `cellar` is `:any` or `:any_skip_relocation` prefix should be omitted.
+See description of `cellar`. When `cellar` is `:any` or `:any_skip_relocation` the prefix should be omitted.
 
 ### Rebuild version (`rebuild`)
 Optionally contains the rebuild version of the bottle.
-Sometimes bottles may need be updated without bumping the version of the formula e.g. a new patch was applied. In that case the rebuild will have a value of 1 or more.
+Sometimes bottles may need be updated without bumping the version of the formula, e.g. a new patch was applied. In that case the rebuild will have a value of 1 or more.
 
 ### Checksum (`sha256`)
-Contains the SHA-256 of bottle for a particular version of macOS.
+Contains the SHA-256 hash of a bottle for a particular version of macOS.
 
 ## Formula DSL
 Additionally there is a method available in the formula DSL.
 
-### Pour Bottle (`pour_bottle?`)
+### Pour bottle (`pour_bottle?`)
 Optionally returns a boolean to decide whether a bottle should be used for this formula.
-For example a bottle may break if another formula has been compiled with non-default options so this method could check for that case and return `false`.
+For example a bottle may break if another formula has been compiled with non-default options, so this method could check for that case and return `false`.
 
 A full example:
 
@@ -77,5 +77,5 @@ pour_bottle? do
 end
 ```
 
-## Planned Improvements
+## Planned improvements
 Most bottle features have been (and planned improvements will be) implemented by @MikeMcQuaid. Contact him directly with questions.