Merge branch 'master' into keco/add-set-access-level-doc

pages/commands/rush_change.md

@@ -7,7 +7,7 @@ navigation_source: docs_nav
 ```
 usage: rush change [-h] [-v] [-b BRANCH]
 
-Asks a series of questions and then generates a <branchname>-<timstamp>.json
+Asks a series of questions and then generates a <branchname>-<timestamp>.json
 file in the common folder. The `publish` command will consume these files and
 perform the proper version bumps. Note these changes will eventually be
 published in a changelog.md file in each package. The possible types of

pages/configs/command_line_json.md

@@ -4,7 +4,7 @@ title: command-line.json
 navigation_source: docs_nav
 ---
 
-This is the template that `rush init` generates for **./commnon/config/rush/command-line.json**:
+This is the template that `rush init` generates for **./common/config/rush/command-line.json**:
 
 ```js
 /**

pages/configs/common_versions_json.md

@@ -4,7 +4,7 @@ title: common-versions.json
 navigation_source: docs_nav
 ---
 
-This is the template that `rush init` generates for **./commnon/config/rush/common-versions.json**:
+This is the template that `rush init` generates for **./common/config/rush/common-versions.json**:
 
 ```js
 /**

pages/configs/npmrc.md

@@ -4,7 +4,7 @@ title: .npmrc
 navigation_source: docs_nav
 ---
 
-This is the template that `rush init` generates for **./commnon/config/rush/.npmrc**:
+This is the template that `rush init` generates for **./common/config/rush/.npmrc**:
 
 ```shell
 # Rush uses this file to configure the package registry, regardless of whether the

pages/configs/pnpmfile_js.md

@@ -4,7 +4,7 @@ title: pnpmfile.js
 navigation_source: docs_nav
 ---
 
-This is the template that `rush init` generates for **./commnon/config/rush/pnpmfile.js**:
+This is the template that `rush init` generates for **./common/config/rush/pnpmfile.js**:
 
 ```js
 "use strict";

pages/configs/version_policies_json.md

@@ -4,7 +4,7 @@ title: version-policies.json
 navigation_source: docs_nav
 ---
 
-This is the template that `rush init` generates for **./commnon/config/rush/version-policies.json**:
+This is the template that `rush init` generates for **./common/config/rush/version-policies.json**:
 
 ```js
 /**

pages/help/faq.md

@@ -67,3 +67,7 @@ Without Rush, NPM looks for "**.npmrc**" in these two places, *and merges their
 When Rush invokes "npm install", it looks for "**.npmrc**" in these two places:
 - "**./common/config/rush/.npmrc**" (which gets copied to "**./common/temp/.npmrc**" during install)
 - in your user home directory
+
+### Why do Rush's JSON config files contain `//` comments that GitHub shows in red?
+
+Obviously config files need to be documented.  We're trying to figure out a better way to handle this.  See [issue #1088](https://github.com/Microsoft/web-build-tools/issues/1088) for a proposal.