Merge pull request #3168 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to master to sync with https://github.com/MicrosoftDocs/visualstudio-docs (branch master)

Author: gewarren

docs/javascript/configure-packages-with-package-json.md

@@ -22,7 +22,7 @@ The npm package versioning system has strict rules. The version format follows h
 
     [major].[minor].[patch]
 
-Let's say you have a package in your app with a version of 5.2.1. 5 is the major version, 2 is the minor version, and 1 is the patch.
+Let's say you have a package in your app with a version of 5.2.1. The major version is 5, the minor version is 2, and the patch is 1.
 
 * In a major version update, the package includes new features that are backwards-incompatible, that is, breaking changes.
 * In a minor version update, new features have been added to the package that are backwards-compatible with earlier package versions.
@@ -67,4 +67,4 @@ Using this notation, npm can update react 16.4.2 to 16.5.0 (or 16.5.1, 16.6.0, e
 
 When npm updates packages, it generates a *package-lock.json* file, which lists the actual npm package versions used in your app, including all nested packages. While *package.json* controls the direct dependencies for your app, it does not control nested dependencies (other npm packages required by a particular npm package). You can use the *package-lock.json* file in your development cycle if you need to make sure that other developers and testers are using the exact packages that you are using, including nested packages. For more information, see [package-lock.json](https://docs.npmjs.com/files/package-lock.json) in the npm documentation.
 
-For Visual Studio, the *package-lock.json* file is not added to your project, but you can find it in the project folder.
+For Visual Studio, the *package-lock.json* file is not added to your project, but you can find it in the project folder.