(doc) Powershell -> PowerShell

BuildScripts/releaseNotes.xml

@@ -1,6 +1,6 @@
 <releaseNotes>
 - Revert vendored Chocolatey to stable 0.10.5
 - Add a ShowRibbon for Windows Explorer
-- Use System.IO.Compression.FileSystem for boxstarter module expansion on modern Powershell versions
+- Use System.IO.Compression.FileSystem for boxstarter module expansion on modern PowerShell versions
 - Add file64 param to fix 64 bit binary installs
 </releaseNotes>

README.md

@@ -11,7 +11,7 @@ Repeatable, reboot resilient windows environment installations made easy using C
 * Integrates with Hyper-V and Windows Azure VMs supporting checkpoint restore and creation
 * Installation packages build on top of [Chocolatey](https://chocolatey.org) package management
 * Easily install with just a [Gist and the Boxstarter Web Launcher](https://boxstarter.org/WebLauncher) or [create a private repository on a thumb drive or network share](https://boxstarter.org/InstallingPackages#InstallFromShare)
-* Works on Window 7/2008 R2 and up with Powershell 2.0 and higher
+* Works on Window 7/2008 R2 and up with PowerShell 2.0 and higher
 * Lots of Windows configuration utilities including installing critical updates, changing windows explorer options, and more.
 
 ## Quickly install your favorite applications and settings, on any machine, with a gist! No pre-installed software needed.
@@ -46,7 +46,7 @@ Install-BoxstarterPackage -ComputerName win7 `
 
 ![Remote Install](Web/Images/result.png)
 
-**NOTE:** PowerShell Remoting must be enabled on the remote machine. Launch a Powershell Console as administrator:
+**NOTE:** PowerShell Remoting must be enabled on the remote machine. Launch a PowerShell Console as administrator:
 
 ```powershell
 Enable-PSRemoting -Force

Web/InstallingPackages.cshtml

@@ -149,7 +149,7 @@ $result = (new-Object -TypeName BoxstarterConnectionConfig -ArgumentList machine
 </pre>
 <h3>Troubleshooting Remote Installations</h3>
 <h4>Establishing remote connections with servers not on the local subnet</h4>
-<p>By default,  server versions of Windows have a firewall rule restricting traffic that is not on the local subnet. There may be circumstances where you might want to connect over the public Internet to another machine. This can be done by manually enabling the "WINRM-HTTP-In-TCP-PUBLIC" firewall rule using the Powershell 3.0 <code>Set-NetFirewallRule</code> or the command line <code>netsh advfirewall</code> command.</p>
+<p>By default,  server versions of Windows have a firewall rule restricting traffic that is not on the local subnet. There may be circumstances where you might want to connect over the public Internet to another machine. This can be done by manually enabling the "WINRM-HTTP-In-TCP-PUBLIC" firewall rule using the PowerShell 3.0 <code>Set-NetFirewallRule</code> or the command line <code>netsh advfirewall</code> command.</p>
 <p>Client versions of Windows will only allow PSRemoting on Private and Domain networks. Clients on PowerShell 3.0 and higher can provide the <code>-SkipNetorkProfileCheck</code> to Enable-PSRemoting to allow connections to public computers on the local subnet. Boxstarter uses this parameter when enabling Remoting on clients. Like with Server versions, you can enable a firewall rule to work around the local subnet restriction. </p>
 <p>Windows 7 OSs running PowerShell 2.0 can not enable PSRemoting when on a public network connection. You will need to change your connection type to a private or Domain based connection.</p>
 

Web/Learn/RemotePackageWithArtifacts.cshtml

@@ -23,7 +23,7 @@
 <h3>Step 3</h3>
 <h4><span class="text-primary">Invoke the Boxstarter shell</span></h4>
 <img src="~/Images/shortcut.png">
-<p>The Boxstarter install creates a shortcut to a shell that provides the easiest way to access Boxstarter commands especially if you are not familiar with Powershell. See <a href="~/UsingBoxstarter">Using Boxstarter Commands</a> for information about running Boxstarter in your own shell.</p>
+<p>The Boxstarter install creates a shortcut to a shell that provides the easiest way to access Boxstarter commands especially if you are not familiar with PowerShell. See <a href="~/UsingBoxstarter">Using Boxstarter Commands</a> for information about running Boxstarter in your own shell.</p>
 
 <h3>Step 4</h3>
 <h4><span class="text-primary">Create the Package</span></h4>
@@ -80,7 +80,7 @@ try {
 <pre>Invoke-BoxstarterBuild -Name NugetServer</pre>
 
 <h3>Step 7</h3>
-<h4><span class="text-primary">Ensure Powershell Remoting is enabled on the target machine</span></h4>
+<h4><span class="text-primary">Ensure PowerShell Remoting is enabled on the target machine</span></h4>
 <p>In many cases this step is unnecessary. If you are using either the builtin administrator account or a domain account with admin privileges on a server operating system, remoting is on by default. Otherwise, run the following command on the machine with a user who has admin privileges:</p>
 <pre>Enable-PSRemoting -Force</pre>
 

Web/Learn/SimplePackage.cshtml

@@ -17,7 +17,7 @@
 
 <h3>Step 2</h3>
 <h4><span class="text-primary">Create your installer script</span></h4>
-<p>Open your favorite text editor and compose your installer. Although this can contain any valid Powershell, you really do not need to know any Powershell to create your script. This could just be a collection of Boxstarter commands. Here is an example:</p>
+<p>Open your favorite text editor and compose your installer. Although this can contain any valid PowerShell, you really do not need to know any PowerShell to create your script. This could just be a collection of Boxstarter commands. Here is an example:</p>
 <pre>
 Set-WindowsExplorerOptions -EnableShowHiddenFilesFoldersDrives -EnableShowProtectedOSFiles -EnableShowFileExtensions
 Enable-RemoteDesktop
@@ -35,7 +35,7 @@ Install-WindowsUpdate -AcceptEula
 <h3>Step 3</h3>
 <h4><span class="text-primary">Invoke the Boxstarter shell</span></h4>
 <img src="~/Images/shortcut.png">
-<p>The Boxstarter install creates a shortcut to a shell that provides the easiest way to access Boxstarter commands especially if you are not familiar with Powershell. See <a href="~/UsingBoxstarter">Using Boxstarter Commands</a> for information about running Boxstarter in your own shell.</p>
+<p>The Boxstarter install creates a shortcut to a shell that provides the easiest way to access Boxstarter commands especially if you are not familiar with PowerShell. See <a href="~/UsingBoxstarter">Using Boxstarter Commands</a> for information about running Boxstarter in your own shell.</p>
 
 <h3>Step 4</h3>
 <h4><span class="text-primary">Convert your Script to a Package</span></h4>

deployment.md

@@ -20,7 +20,7 @@ Now Build the artifacts from the root of the repository:
 ./build quick-deploy
 ```
 
-If this is the first time you are running this command, it may take extra time to run as it ensures all prerequisites are installed (VS build tools, Azure Powershell module, etc.).
+If this is the first time you are running this command, it may take extra time to run as it ensures all prerequisites are installed (VS build tools, Azure PowerShell module, etc.).
 
 This will compile the Boxstarter website and ClickOnce application and also sign the ClickOnce app. It will bump the version where the build version will be the number of commits since the minor version was tagged. It will update the Boxstarter homepage HTML to reflect this version and create new Chocolatey packages for all Boxstarter packages.