Documentation clean up and consistency; closes #17625

[skip sauce]

diff --git a/README.md b/README.md
index 0d1350cd851edc4acb11ee1df92761b0fbb742a8..4ca1880971b7de8dfe51152d18d949bb26e96e13 100644 (file)
--- a/README.md
+++ b/README.md
@@ -11,6 +11,7 @@ Bootstrap is a sleek, intuitive, and powerful front-end framework for faster and
 
 To get started, check out <http://getbootstrap.com>!
 
+
 ## Table of contents
 
 * [Quick start](#quick-start)
@@ -22,6 +23,7 @@ To get started, check out <http://getbootstrap.com>!
 * [Creators](#creators)
 * [Copyright and license](#copyright-and-license)
 
+
 ## Quick start
 
 Several quick start options are available:
@@ -64,7 +66,6 @@ bootstrap/
 We provide compiled CSS and JS (`bootstrap.*`), as well as compiled and minified CSS and JS (`bootstrap.min.*`). CSS [source maps](https://developer.chrome.com/devtools/docs/css-preprocessors) (`bootstrap.*.map`) are available for use with certain browsers' developer tools. Fonts from Glyphicons are included, as is the optional Bootstrap theme.
 
 
-
 ## Bugs and feature requests
 
 Have a bug or a feature request? Please first read the [issue guidelines](https://github.com/twbs/bootstrap/blob/master/CONTRIBUTING.md#using-the-issue-tracker) and search for existing and closed issues. If your problem or idea is not addressed yet, [please open a new issue](https://github.com/twbs/bootstrap/issues/new).
@@ -76,7 +77,7 @@ Bootstrap's documentation, included in this repo in the root directory, is built
 
 ### Running documentation locally
 
-1. If necessary, [install Jekyll](http://jekyllrb.com/docs/installation) (requires v2.5.x).  
+1. If necessary, [install Jekyll](http://jekyllrb.com/docs/installation) (requires v2.5.x).
    **Note for Windows users:** Read [this unofficial guide](http://jekyll-windows.juthilo.com/) to get Jekyll up and running without problems.
 2. Install the Ruby-based syntax highlighter, [Rouge](https://github.com/jneen/rouge), with `gem install rouge`.
 3. From the root `/bootstrap` directory, run `jekyll serve` in the command line.
@@ -91,7 +92,6 @@ Documentation for v2.3.2 has been made available for the time being at <http://g
 [Previous releases](https://github.com/twbs/bootstrap/releases) and their documentation are also available for download.
 
 
-
 ## Contributing
 
 Please read through our [contributing guidelines](https://github.com/twbs/bootstrap/blob/master/CONTRIBUTING.md). Included are directions for opening issues, coding standards, and notes on development.
@@ -101,7 +101,6 @@ Moreover, if your pull request contains JavaScript patches or features, you must
 Editor preferences are available in the [editor config](https://github.com/twbs/bootstrap/blob/master/.editorconfig) for easy use in common text editors. Read more and download plugins at <http://editorconfig.org>.
 
 
-
 ## Community
 
 Get updates on Bootstrap's development and chat with the project maintainers and community members.
@@ -114,7 +113,6 @@ Get updates on Bootstrap's development and chat with the project maintainers and
 * Developers should use the keyword `bootstrap` on packages which modify or add to the functionality of Bootstrap when distributing through [npm](https://www.npmjs.com/browse/keyword/bootstrap) or similar delivery mechanisms for maximum discoverability.
 
 
-
 ## Versioning
 
 For transparency into our release cycle and in striving to maintain backward compatibility, Bootstrap is maintained under [the Semantic Versioning guidelines](http://semver.org/). Sometimes we screw up, but we'll adhere to those rules whenever possible.
@@ -122,7 +120,6 @@ For transparency into our release cycle and in striving to maintain backward com
 See [the Releases section of our GitHub project](https://github.com/twbs/bootstrap/releases) for changelogs for each release version of Bootstrap. Release announcement posts on [the official Bootstrap blog](http://blog.getbootstrap.com) contain summaries of the most noteworthy changes made in each release.
 
 
-
 ## Creators
 
 **Mark Otto**
@@ -136,7 +133,6 @@ See [the Releases section of our GitHub project](https://github.com/twbs/bootstr
 * <https://github.com/fat>
 
 
-
 ## Copyright and license
 
 Code and documentation copyright 2011-2015 Twitter, Inc. Code released under [the MIT license](https://github.com/twbs/bootstrap/blob/master/LICENSE). Docs released under [Creative Commons](https://github.com/twbs/bootstrap/blob/master/docs/LICENSE).

diff --git a/js/tests/README.md b/js/tests/README.md
index 6cdb41059bc9db2db219448b8c91ba6c2aed3b53..9b2f18296f9a74992495c237b81b14ba4fbac8f2 100644 (file)
--- a/js/tests/README.md
+++ b/js/tests/README.md
@@ -20,6 +20,7 @@ To run the unit test suite via a real web browser, open `index.html` in the brow
 
 **Note:** Your new unit tests should fail before your changes are applied to the plugin, and should pass after your changes are applied to the plugin.
 
+
 ## What should a unit test look like?
 
 * Each test should have a unique name clearly stating what unit is being tested.

diff --git a/test-infra/README.md b/test-infra/README.md
index ce7d74b6583cfa9d5b2ca9cf7a637743180ea44a..366f023b8787d23fe108d1e5a11aebbd8e1de338 100644 (file)
--- a/test-infra/README.md
+++ b/test-infra/README.md
@@ -7,7 +7,7 @@ The SHA-256 hash of the single file is used as the key for the cache. The direct
 
 All the tarballs are stored in S3's Reduced Redundancy Storage (RRS) storage class, since this is cheaper and the data is non-critical.
 
-`s3_cache.py` itself never deletes cache entries; deletion should either be done manually or using automatic S3 lifecycle rules on the bucket.
+`s3_cache.py` itself never deletes cache entries; deletion should either be done manually or using automatic S3 life cycle rules on the bucket.
 
 Similar to git, `s3_cache.py` makes the assumption that [SHA-256 will effectively never have a collision](https://stackoverflow.com/questions/4014090/is-it-safe-to-ignore-the-possibility-of-sha-collisions-in-practice).
 
@@ -51,7 +51,7 @@ If it had to `generate` the cache, it will later create a tarball of the `cache`
 1. Create an Amazon Web Services (AWS) account.
 2. Create an Identity & Access Management (IAM) user, and note their credentials.
 3. Create an S3 bucket.
-4. Set permissions on the bucket to grant the user read+write access.
+4. Set permissions on the bucket to grant the user read + write access.
 5. Set the user credentials as secure Travis environment variables.
 
 ### In detail
@@ -70,7 +70,7 @@ If it had to `generate` the cache, it will later create a tarball of the `cache`
 
 9. Determine and note what your bucket's ARN is. The ARN for an S3 bucket is of the form: `arn:aws:s3:::the-bucket-name-goes-here`
 10. In the bucket's Properties pane, in the "Permissions" section, click the "Edit bucket policy" button.
-11. Input and submit an IAM Policy that grants the user at least read+write rights to the bucket. AWS has a policy generator and some examples to help with crafting the policy. Here's the policy that Bootstrap uses, with the sensitive bits censored:
+11. Input and submit an IAM Policy that grants the user at least read + write rights to the bucket. AWS has a policy generator and some examples to help with crafting the policy. Here's the policy that Bootstrap uses, with the sensitive bits censored:
 
     ```json
     {