diff --git a/release-notes/2.1/2.1.0-known-issues.md b/release-notes/2.1/2.1.0-known-issues.md
index 9dea62b5..004d08c5 100644
--- a/release-notes/2.1/2.1.0-known-issues.md
+++ b/release-notes/2.1/2.1.0-known-issues.md
@@ -4,7 +4,7 @@ This document lists known issues for **.NET Core 2.1 RC 1** which may be encount
 
 ## Runtime
 
-core-setup/4149](https://github.com/dotnet/core-setup/issues/4149
+[core-setup/4149](https://github.com/dotnet/core-setup/issues/4149)
 
 On Unix, if $TMPDIR is set to a nonexistent or non writeable location, your app will log "Failed to initialize CoreCLR, HRESULT: 0x80004005" to the console and fail to start.
 
@@ -28,7 +28,7 @@ Also: Ensure that global.json does not pin to .NET Core SDK 2.1.300 Preview 1 on
 
 *Workaround* - Upgrade to target .NET Core Runtime 2.1
 
-** Global tools install succeeds on Mac and Linux but fails to run **
+**Global tools install succeeds on Mac and Linux but fails to run**
 
 [cli/9319](https://github.com/dotnet/cli/issues/9319)
 
@@ -36,7 +36,7 @@ Installing a Global Tool using --tool-path with a relative path on Mac and Linux
 
 This occurs because the relative path is calculated incorrectly.
 
-*Workaround - Specify the full path for the  --tool-path option. For example
+*Workaround* - Specify the full path for the  --tool-path option. For example
  
 - `dotnet tool install dotnetsay --tool-path /home/build/tools`
  
@@ -54,4 +54,4 @@ We have temporarily removed the RC 1 installers from the Linux package feeds unt
 
 ```bash
 sudo apt install dotnet-host=2.0.6-1
-```
\ No newline at end of file
+```