Copy edited.
Replace ascii cue to visual cue

Change old school ascii "underline" style cue to a visual cue by writing installing package title in brighter green.

This is especially convenient when you install 10 packages at once.

Just a proposition. Pending review.

See #374 @ https://github.com/chocolatey/chocolatey/issues/374
Fixed Issue where the 32-bit DISM will be called on a 64-bit OS when running a 32-bit shell/process
Fixed issue 378 where DISM is missing because of a missing newline in the command passed to the elevated shell and by specifying the exact path to the DISM tool instead of relying of the path of the system.
Fixed problem where CPU bits mismatches OS bits

Now looking at OS in stead of CPU.
Bonus: Skipping CPU is faster. Trying fallback for older OS.
I am on Linux, so I have only tested this using my common sense VM.
(#411) added logout parameter and forced write-host to honor that parameter
(#411) changed logout to quiet
add CreateNoWindow  to Run-NuGet.ps1
Merge pull request #450 from SimonCropp/master

add CreateNoWindow  to Run-NuGet.ps1
Generate _env.cmd file instead of bat file for consistency.
Merge pull request #469 from pagebrooks/fix-env-batch-file-consistency

Generate _env.cmd file instead of bat file for consistency.
added functionality to support installArguments in packages.config

This Pull Requests add an additional attribute to the package.config named "installArguments".
This attribute basically does the same as you would provide the "installArguments" paramer
 to the "chocolatey install" command.
tests: fix Install-ChocolateyShortcut tests with non-default Chocolatey install path

Replace hardcoded C:\Chocolatey with $Env:ChocolateyInstall.
build tools: use 64-bit msbuild if present

This makes build.bat behavior consistent with that of test.cmd with
respect to bitness of PowerShell used to run tests.

Otherwise, test.cmd would run tests using 64-bit PowerShell, while
build.bat would run them using 32-bit PowerShell (via 32-bit msbuild).
build tools: fix building the nupkg with non-default Chocolatey install path

Replace hardcoded %systemdrive%\Chocolatey with %ChocolateyInstall%.
add CreateNoWindow  to Run-NuGet.ps1
Generate _env.cmd file instead of bat file for consistency.
tests: remove chocolateyInstaller module at test initialization

The existing test init code removes the 'chocolatey' and '_Setup' modules,
but leaves the 'chocolateyInstaller' module loaded. This has the nasty
effect that changes to chocolatey helpers are ignored when tests are
repeatedly run in the same Powershell session using Invoke-Pester.

As 'chocolateyInstaller' is imported as a nested module (by the
'chocolatey' module), it requires the -All switch to Get-Module in order
to be discovered and must be removed by piping it to Remove-Module.

Also change the existing module removal commands to pipe syntax, so as not
to mix two removal styles in one file (and get tighter code).
add basic tests for Get-ChocolateyUnzip
Write-FileUpdateLog: support passing arguments to the script block