From 8285bb0c747090e0f97acaa86232ae9a7a68d061 Mon Sep 17 00:00:00 2001 From: SteveSandersonMS Date: Fri, 21 Oct 2016 15:10:30 +0100 Subject: [PATCH] Some extra links in docs --- src/Microsoft.AspNetCore.SpaServices/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/Microsoft.AspNetCore.SpaServices/README.md b/src/Microsoft.AspNetCore.SpaServices/README.md index f9d76ad..2ae2692 100644 --- a/src/Microsoft.AspNetCore.SpaServices/README.md +++ b/src/Microsoft.AspNetCore.SpaServices/README.md @@ -671,10 +671,10 @@ This is not a perfect solution to the problem of identifying 404s, because for e How to attach and use a debugger depends on what code you want to debug. For details, see: - * How to debug your C# code that runs on the server + * [How to debug your C# code that runs on the server](#debugging-your-c-code-that-runs-on-the-server) * How to debug your JavaScript/TypeScript code: - * ... when it's running in a browser - * ... when it's running on the server (i.e., via `asp-prerender` or NodeSevices) + * ... [when it's running in a browser](#debugging-your-javascripttypescript-code-when-its-running-in-a-browser) + * ... [when it's running on the server](#debugging-your-javascripttypescript-code-when-it-runs-on-the-server) (i.e., via `asp-prerender` or NodeSevices) ### Debugging your C# code that runs on the server