Misc code formatting and other corrections

Kraig Brockschmidt · Kraig Brockschmidt · commit bc853e0b0af6 · 2017-01-10T12:04:18.000-08:00
diff --git a/docs/Consume-Packages/Reinstalling-and-Updating-Packages.md b/docs/Consume-Packages/Reinstalling-and-Updating-Packages.md
@@ -34,13 +34,17 @@ There are a number of situations, described below under [When to Reinstall a Pac
 
 Being mindful of the [Considerations](#considerations) described later, you can easily reinstall any package using the following command in the Visual Studio Package Manager Console (**Tools** > **NuGet Package Manager** > **Package Manager Console**):
 
+```ps
     Update-Package –reinstall <package_name>
+```
 
 Using this command is much easier than removing a package and then trying to locate the same package in the NuGet gallery with the same version.
 
 The same command without `-reinstall` will update a package to a newer version, if applicable:
 
+```ps
     Update-Package <package_name>
+```
 
 Any updates are subject to version constraints indicated in `packages.config`, as described below in [Constraining upgrade versions](#constraining-upgrade-versions), but do not apply to projects using `project.json`.
 
diff --git a/docs/Consume-Packages/Team-Foundation-Build.md b/docs/Consume-Packages/Team-Foundation-Build.md
@@ -52,7 +52,7 @@ NuGet has supported [restoring packages](../consume-packages/package-restore.md)
 
 The cure to this problem is making sure that packages are restored as the first step in the build process. NuGet 2.7+ makes this easy via a simplified command line:
 
-    nuget.exe restore path\to\solution.sln
+    nuget restore path\to\solution.sln
 
 When your build process restores packages before building the code, you don't need to check-in **.targets** files
 
@@ -86,7 +86,7 @@ The structure of the repository looks as follows:
         │
         └───tools
             └───NuGet
-                    NuGet.exe
+                    nuget.exe
 
 You can see that we haven't checked-in the `packages` folder nor any **.targets** files.
 
diff --git a/docs/Create-Packages/project.json-Impact.md b/docs/Create-Packages/project.json-Impact.md
@@ -32,9 +32,6 @@ ms.reviewer:
 
 The project.json system used in NuGet 3.x affects package authors in several ways as described in the following sections.
 
-- [Install and uninstall scripts are ignored](#install-and-uninstall-scripts-are-ignored)
-
-
 ## Changes affecting existing packages usage
 
 Traditional NuGet packages support a set of features that are not carried over to the transitive world.
diff --git a/docs/Policies/NuGet-FAQ.md b/docs/Policies/NuGet-FAQ.md
@@ -100,7 +100,9 @@ The console provides a variable named `$DTE` that returns the `DTE` object. See
 
 This is a known issue with how PowerShell interacts with a COM object. Try the following:
 
+```ps
     `$dte2 = Get-Interface $dte ([EnvDTE80.DTE2])`
+```
 
 `Get-Interface` is a helper function added by the NuGet PowerShell host.
 
diff --git a/docs/Release-Notes/Known-Issues.md b/docs/Release-Notes/Known-Issues.md
@@ -61,17 +61,19 @@ The NuGet.config file in your `%AppData%\NuGet\` folder has accidentally been em
 
 In NuGet 2.7 or above, when you attempt to install any package which contains assembly references, you may receive the error message **"Input string was not in a correct format."**, like below:
 
-    PM> install-package log4net
-     Installing 'log4net 2.0.0'.
-     Successfully installed 'log4net 2.0.0'.
-     Adding 'log4net 2.0.0' to Tyson.OperatorUpload.
-     Install failed. Rolling back...
-     install-package : Input string was not in a correct format.
-     At line:1 char:1
-    ◾install-package log4net
-    ◾ ~~~~~~~~~~~~~~~~~~~~~~~
-    ◾CategoryInfo : NotSpecified: (:) [Install-Package], FormatException
-    ◾ FullyQualifiedErrorId : NuGetCmdletUnhandledException,NuGet.PowerShell.Commands.InstallPackageCommand
+```ps
+    install-package log4net
+      Installing 'log4net 2.0.0'.
+      Successfully installed 'log4net 2.0.0'.
+      Adding 'log4net 2.0.0' to Tyson.OperatorUpload.
+      Install failed. Rolling back...
+      install-package : Input string was not in a correct format.
+      At line:1 char:1
+          install-package log4net
+          ~~~~~~~~~~~~~~~~~~~~~~~
+         CategoryInfo : NotSpecified: (:) [Install-Package], FormatException
+         FullyQualifiedErrorId : NuGetCmdletUnhandledException,NuGet.PowerShell.Commands.InstallPackageCommand
+```
 
 
 This is caused by the type library for the VSLangProj.dll COM component being unregistered on your system. This can happen, for example, when you have two versions of Visual Studio installed side-by-side and you then uninstall the older version. Doing so may inadvertently unregister the above COM library.
diff --git a/docs/Release-Notes/NuGet-2.5.md b/docs/Release-Notes/NuGet-2.5.md
@@ -190,15 +190,15 @@ Starting with NuGet 2.5, if NuGet.exe identifies a UNC/folder source, it will pe
 
 The following command will now work:
 
-    NuGet.exe push -source \\mycompany\repo\ mypackage.1.0.0.nupkg
+    nuget push -source \\mycompany\repo\ mypackage.1.0.0.nupkg
 
 ## NuGet.exe supports explicitly-specified Config files
 
 NuGet.exe commands that acccess configuration (all except 'spec' and 'pack') now support a new '-ConfigFile' option, which forces a specific config file to be used in place of the default config file at %AppData%\nuget\nuget.config.
 
 Example:
 
-    NuGet.exe sources add -name test -source http://test -ConfigFile C:\test\.nuget\nuget.config
+    nuget sources add -name test -source http://test -ConfigFile C:\test\.nuget\nuget.config
 
 ## Support for Native projects
 
diff --git a/docs/Schema/msbuild-targets.md b/docs/Schema/msbuild-targets.md
@@ -63,33 +63,33 @@ Similarly, you can write an MSBuild task, write your own target and consume NuGe
 In order for MSBuild to be able to gather all the inputs, all metadata from `project.json` and `.nuspec` will move into the `.csproj` file. The table below describes the MSBuild properties that can be added to a `.csproj` file within the first &lt;PropertyGroup&gt; node. You can make these edits easily in Visual Studio 2017 and later by right-clicking the project and selecting **Edit {project_name}** on the context menu. For convenience the table is organized by the equivalent property in a [`.nuspec` file](../schema/nuspec.md).
 
 
-| Attribute/NuSpec Value | MSBuild Property | Default | Notes          
-| Id | PackageId | AssemblyName | $(AssemblyName) from msbuild
-| Version | PackageVersion | Version | New $(Version) property from msbuild, is semver compatible. Could be “1.0.0”, “1.0.0-beta”, or “1.0.0-beta-00345”.
-| Authors | Authors | username of the current user will be the default value |
-| Owners | N/A | Not present in NuSpec |
-| Description | Description | "Package Description" |
-| Copyright | Copyright | empty |
-| RequireLicenseAcceptance | PackageRequireLicenseAcceptance | false |
-| LicenseUrl | PackageLicenseUrl | empty |
-| ProjectUrl | PackageProjectUrl | empty |
-| IconUrl | PackageIconUrl | empty |
-| Tags | PackageTags | empty |
-| ReleaseNotes | PackageReleaseNotes | empty |
-| RepositoryUrl | RepositoryUrl | empty |
-| RepositoryType | RepositoryType | empty |
-| PackageType | `&lt;PackageType&gt;DotNetCliTool, 1.0.0.0;Dependency, 2.0.0.0&lt;/PackageType&gt;` |  |
-| Title | Not supported | |
-| Summary | Not supported | |
-| n/a | PackageOutputPath | The bin\{configuration} folder |
-| n/a | Configuration | Debug |
-| n/a | AssemblyName | |
-| n/a | IncludeSymbols | |
-| n/a | IncludeSource | | If true, there must also be a &lt;SourceFile&gt; node.
-| n/a | IsTool | |
-| n/a | NoPackageAnalysis | |
-| n/a | MinClientVersion | |
-| n/a | TargetPath<br>TargetFramework | | See <a href="#cross-targeting">cross-targeting</a> below.
+| Attribute/NuSpec Value | MSBuild Property | Default | Notes |
+| Id | PackageId | AssemblyName | $(AssemblyName) from msbuild |
+| Version | PackageVersion | Version | New $(Version) property from msbuild, is semver compatible. Could be “1.0.0”, “1.0.0-beta”, or “1.0.0-beta-00345”. |
+| Authors | Authors | username of the current user will be the default value | |
+| Owners | N/A | Not present in NuSpec | |
+| Description | Description | "Package Description" | |
+| Copyright | Copyright | empty | |
+| RequireLicenseAcceptance | PackageRequireLicenseAcceptance | false | |
+| LicenseUrl | PackageLicenseUrl | empty | |
+| ProjectUrl | PackageProjectUrl | empty | |
+| IconUrl | PackageIconUrl | empty | |
+| Tags | PackageTags | empty | |
+| ReleaseNotes | PackageReleaseNotes | empty | |
+| RepositoryUrl | RepositoryUrl | empty | |
+| RepositoryType | RepositoryType | empty | |
+| PackageType | `<PackageType>DotNetCliTool, 1.0.0.0;Dependency, 2.0.0.0</PackageType>` | | |
+| Title | Not supported | | |
+| Summary | Not supported | | |
+| n/a | PackageOutputPath | The bin\{configuration} folder | |
+| n/a | Configuration | Debug | |
+| n/a | AssemblyName | | |
+| n/a | IncludeSymbols | | |
+| n/a | IncludeSource | | If true, there must also be a &lt;SourceFile&gt; node. |
+| n/a | IsTool | | |
+| n/a | NoPackageAnalysis | | |
+| n/a | MinClientVersion | | |
+| n/a | TargetPath<br>TargetFramework | | See <a href="#cross-targeting">cross-targeting</a> below. |
 
 ## pack scenarios
 
@@ -190,23 +190,23 @@ As part of the move to MSBuild, package restore becomes an MSBuild target; `nuge
 
 Additional restore settings may come from MSBuild properties; values are set from the command line.
 
-| Property | Description
-| RestoreSources | List of package sources separated by semicolons
-| RestorePackagesPath | User packages directory path
-| RestoreDisableParallel | Limit downloads to one at a time
-| RestoreConfigFile | nuget.config file
-| RestoreNoCache | If true, avoids using the web cache
-| RestoreIgnoreFailedSource | If true, ignores failing or missing package sources
+| Property | Description |
+| RestoreSources | List of package sources separated by semicolons |
+| RestorePackagesPath | User packages directory path |
+| RestoreDisableParallel | Limit downloads to one at a time |
+| RestoreConfigFile | nuget.config file |
+| RestoreNoCache | If true, avoids using the web cache |
+| RestoreIgnoreFailedSource | If true, ignores failing or missing package sources |
 
 
 ### Restore outputs
 
 Restore creates the following files in the build `obj` folder:
 
-| File | Description
-| project.assets.json | Previously project.lock.json
-| {projectName}.projectFileExtension.nuget.g.props | References to msbuild targets contained in packages
-| {projectName}.projectFileExtension.nuget.g.targets | References to msbuild props contained in packages
+| File | Description |
+| project.assets.json | Previously project.lock.json |
+| {projectName}.projectFileExtension.nuget.g.props | References to msbuild targets contained in packages |
+| {projectName}.projectFileExtension.nuget.g.targets | References to msbuild props contained in packages |
 
 ## PackageTargetFallback
 
diff --git a/docs/Schema/nuget.config-file.md b/docs/Schema/nuget.config-file.md
@@ -87,6 +87,7 @@ http_proxy http_proxy.user http_proxy.password no_proxy | Proxy settings to use
 ## bindingRedirects section
 
 Configures whether NuGet does automatic binding redirects when a package is installed.
+
 Key | Value
 --- | ---
 skip | A Boolean indicating whether to skip automatic binding redirects. The default is false.
diff --git a/docs/Visual-Studio-Extensibility/Project-System-Support.md b/docs/Visual-Studio-Extensibility/Project-System-Support.md
@@ -129,7 +129,7 @@ For example, you might add the following `case` statement to your `IVsHierarchy:
     case __VSHPROPID8.VSHPROPID_ProjectCapabilitiesChecker:
         propVal = new VsProjectCapabilitiesPresenceChecker();
         return VSConstants.S_OK;
-````
+```
 
 
 ## DTE Support
