diff --git a/docs/building/windows-full.md b/docs/building/windows-full.md
index 039431263..f2c74e442 100644
--- a/docs/building/windows-full.md
+++ b/docs/building/windows-full.md
@@ -1,32 +1,27 @@
 Build PowerShell on Windows for .NET Full
 =========================================
 
-This guide supplements the
-[Windows .NET Core instructions](./windows-core.md), as building the
-.NET 4.5.1 (desktop) version is pretty similar.
+This guide supplements the [Windows .NET Core instructions](./windows-core.md), 
+as building the .NET 4.5.1 (desktop) version is pretty similar.
 
 Environment
 ===========
 
-In addition to the dependencies specified in the .NET Core
-instructions, you'll need to:
+In addition to the dependencies specified in the .NET Core instructions, you'll need to:
 
 Install the Visual C++ Compiler via Visual Studio 2015.
 -------------------------------------------------------
 
 This component is required to compile the native `powershell.exe` host.
 
-This is an optionally installed component, so you may need to run the
-Visual Studio installer again.
+This is an optionally installed component, so you may need to run the Visual Studio installer again.
 
-If you don't have any Visual Studio installed, you can use
-[Visual Studio 2015 Community Edition][vs].
+If you don't have any Visual Studio installed, you can use [Visual Studio 2015 Community Edition][vs].
 
 > Compiling with older versions should work, but we don't test it.
 
-**Troubleshooting note:** If `cmake` says that it cannot determine the
-`C` and `CXX` compilers, you either don't have Visual Studio, or you
-don't have the Visual C++ Compiler component installed.
+**Troubleshooting note:** If `cmake` says that it cannot determine the `C` and `CXX` compilers, 
+you either don't have Visual Studio, or you don't have the Visual C++ Compiler component installed.
 
 [vs]: https://www.visualstudio.com/en-us/products/visual-studio-community-vs.aspx
 
@@ -45,8 +40,7 @@ choco install cmake.portable
 Build using our module
 ======================
 
-Use `Start-PSBuild -FullCLR` from the `build.psm1`
-module.
+Use `Start-PSBuild -FullCLR` from the `build.psm1` module.
 
 The output location of `powershell.exe` will be
 
@@ -60,15 +54,15 @@ Build manually
 The build contains the following steps:
 
 - generating Visual Studio project: `cmake`
-- building `powershell.exe` from generated solution: `msbuild
-  powershell.sln`
+- building `powershell.exe` from generated solution: `msbuild powershell.sln`
 - building managed DLLs: `dotnet publish --runtime net451`
 
 
 What can you do with the produced binaries?
 =========================================
 
-**Important**: "We don’t support production deployments of these binaries on any platform". For PowerShell .NET (aka: FullCLR PowerShell) our recommendation is to continue using the PowerShell .NET version already shipping in Windows Client and Windows Server.
+**Important**: "We don’t support production deployments of these binaries on any platform". 
+For PowerShell .NET (aka: FullCLR PowerShell) our recommendation is to continue using the PowerShell .NET version already shipping in Windows Client and Windows Server.
 
 The primary reason to build the PowerShell FullCLR binaries is to test backward compatibility, and interoperability between .NET and CoreCLR.
 It is also important to mention that some features like PowerShell Workflows are not currently available in the CoreCLR version.
@@ -82,10 +76,9 @@ Running Dev version of FullCLR PowerShell
 
 Running FullCLR version is not as simple as CoreCLR version.
 
-If you just run `./powershell.exe`, you will get a `powershell`
-process, but all the interesting DLLs (such as
-`System.Management.Automation.dll`) would be loaded from the Global
-Assembly Cache (GAC), not your output directory.
+If you just run `./powershell.exe`, you will get a `powershell` process, 
+but all the interesting DLLs (such as `System.Management.Automation.dll`) would be loaded from the Global Assembly Cache (GAC), 
+not your output directory.
 
 Use `Start-DevPowerShell` helper function to workaround it with `$env:DEVPATH`