From af975caeed28270c0124c205c2f5016686667648 Mon Sep 17 00:00:00 2001
From: Adam Gauthier <adamgauthier12@gmail.com>
Date: Thu, 28 Jun 2018 17:51:59 -0400
Subject: [PATCH 1/3] Update windows building guide's output folder to
 netcoreapp2.1

---
 docs/building/windows-core.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/building/windows-core.md b/docs/building/windows-core.md
index 54d0a099b17..92755f323db 100644
--- a/docs/building/windows-core.md
+++ b/docs/building/windows-core.md
@@ -58,11 +58,11 @@ Import-Module ./build.psm1
 Start-PSBuild
 ```
 
-Congratulations! If everything went right, PowerShell is now built and executable as `./src/powershell-win-core/bin/Debug/netcoreapp2.0/win7-x64/publish/pwsh`.
+Congratulations! If everything went right, PowerShell is now built and executable as `./src/powershell-win-core/bin/Debug/netcoreapp2.1/win7-x64/publish/pwsh.exe`.
 
 This location is of the form `./[project]/bin/[configuration]/[framework]/[rid]/publish/[binary name]`,
 and our project is `powershell`, configuration is `Debug` by default,
-framework is `netcoreapp2.0`, runtime identifier is `win7-x64` by default,
+framework is `netcoreapp2.1`, runtime identifier is `win7-x64` by default,
 and binary name is `pwsh`.
 The function `Get-PSOutput` will return the path to the executable;
 thus you can execute the development copy via `& (Get-PSOutput)`.

From f0ea3efc435e4394f5a1dc02af3acf1d67e1d291 Mon Sep 17 00:00:00 2001
From: Adam Gauthier <adamgauthier12@gmail.com>
Date: Thu, 28 Jun 2018 19:44:47 -0400
Subject: [PATCH 2/3] Update linux building guide's output folder to
 netcoreapp2.1

---
 docs/building/linux.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/building/linux.md b/docs/building/linux.md
index 55870983860..be37662a19f 100644
--- a/docs/building/linux.md
+++ b/docs/building/linux.md
@@ -71,7 +71,7 @@ Start-PSBuild
 Congratulations! If everything went right, PowerShell is now built.
 The `Start-PSBuild` script will output the location of the executable:
 
-`./src/powershell-unix/bin/Linux/netcoreapp2.0/linux-x64/publish/pwsh`.
+`./src/powershell-unix/bin/Debug/netcoreapp2.1/linux-x64/publish/pwsh`.
 
 You should now be running the PowerShell Core that you just built, if your run the above executable.
 You can run our cross-platform Pester tests with `Start-PSPester`, and our xUnit tests with `Start-PSxUnit`.

From 15d5ff12d1720157e9d07f182ac555cc2ded9286 Mon Sep 17 00:00:00 2001
From: Adam Gauthier <adamgauthier12@gmail.com>
Date: Thu, 28 Jun 2018 20:08:44 -0400
Subject: [PATCH 3/3] Update linux building guide's output folder to
 netcoreapp2.1

---
 docs/building/macos.md | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/docs/building/macos.md b/docs/building/macos.md
index 60b14db5016..2e00b85f0f8 100644
--- a/docs/building/macos.md
+++ b/docs/building/macos.md
@@ -36,5 +36,4 @@ We cannot do this for you in the build module due to #[847][].
 
 Start a PowerShell session by running `pwsh`, and then use `Start-PSBuild` from the module.
 
-After building, PowerShell will be at `./src/powershell-unix/bin/Linux/netcoreapp2.0/osx-x64/publish/powershell`.
-Note that configuration is still `Linux`.
+After building, PowerShell will be at `./src/powershell-unix/bin/Debug/netcoreapp2.1/osx-x64/publish/pwsh`.