From 0087f78c26f3627bb5382d88b0d1ab3db489ed5a Mon Sep 17 00:00:00 2001
From: xtqqczze <45661989+xtqqczze@users.noreply.github.com>
Date: Wed, 29 Apr 2020 04:25:33 +0100
Subject: [PATCH] Update TFM reference in build docs (#12514)

---
 docs/building/linux.md        | 2 +-
 docs/building/macos.md        | 2 +-
 docs/building/windows-core.md | 4 ++--
 3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/building/linux.md b/docs/building/linux.md
index 351f02cef4..2d25af84bb 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/Debug/netcoreapp3.0/linux-x64/publish/pwsh`.
+`./src/powershell-unix/bin/Debug/net5.0/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`.
diff --git a/docs/building/macos.md b/docs/building/macos.md
index d969753e63..e398451e8d 100644
--- a/docs/building/macos.md
+++ b/docs/building/macos.md
@@ -36,4 +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/Debug/netcoreapp3.0/osx-x64/publish/pwsh`.
+After building, PowerShell will be at `./src/powershell-unix/bin/Debug/net5.0/osx-x64/publish/pwsh`.
diff --git a/docs/building/windows-core.md b/docs/building/windows-core.md
index 207f38f085..5e9aa73cf0 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/netcoreapp3.0/win7-x64/publish/pwsh.exe`.
+Congratulations! If everything went right, PowerShell is now built and executable as `./src/powershell-win-core/bin/Debug/net5.0/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 `netcoreapp3.0`, runtime identifier is `win7-x64` by default,
+framework is `net5.0`, 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)`.