Master -> Live

community.md

@@ -45,6 +45,7 @@ Below is a list of projects and resources from the Blazor community (links in ea
 * [BlazeDown](https://github.com/EdCharbeneau/BlazeDown) ([Demo](http://edcharbeneau.com/BlazeDown/)) – An online markdown editor built with Blazor.
 * [Blazor + Electron sample](https://github.com/SteveSandersonMS/BlazorElectronExperiment.Sample) – Explore how a Blazor app can be used to build a cross-platform desktop app.
 * [Blazor + Sitecore](https://github.com/GoranHalvarsson/SitecoreBlazor) ([Blog post](https://visionsincode.wordpress.com/2018/06/30/time-travel-into-the-future-blazor-sitecore-helix/)) – Example of dynamic pages and routes with SiteCore and [Helix](https://helix.sitecore.net/).
+* [Blazor Asteroids](https://github.com/aesalazar/AsteroidsWasm) ([Demo](https://aesalazar.github.io/AsteroidsWasm/)) – The 80's classic video game developed in C# for WinForms/WPF but running Blazor.
 * [Blazor Bricks](https://www.codeproject.com/Articles/1241210/WebAssembly-with-Blazor) – A bricks game developed with C# and Blazor.
 * [Blazor Calculator](https://github.com/Lupusa87/BlazorCalculator) ([Demo](https://lupusassblazordemos.azurewebsites.net)) – Simple calculator with history and ability to use previous results in new calculations.
 * [Blazor Chat sample](https://github.com/conficient/BlazorChatSample) ([Demo](https://blazorchatsample.azurewebsites.net/)) – An app that demonstrates the use of [SignalR](https://docs.microsoft.com/aspnet/core/signalr/) to create a Blazor chat app.

docs/components/index.md

@@ -259,7 +259,7 @@ When the component is rendered, the `loginDialog` field is populated with the `M
 > [!IMPORTANT]
 > The `loginDialog` variable is only populated after the component is rendered and its output includes the `MyLoginDialog` element because until then there is nothing to reference. To manipulate components references after the component has finished rendering, use the `OnAfterRenderAsync` or `OnAfterRender` lifecycle methods.
 
-While capturing component references uses a similar syntax to [capturing element references](xref:client-side/blazor/javascript-interop#capturing-references-to-elements), it isn't a [JavaScript interop](xref:client-side/blazor/javascript-interop) feature. Component references aren't passed to JavaScript code; they're only used in .NET code.
+While capturing component references uses a similar syntax to [capturing element references](xref:client-side/blazor/javascript-interop#capture-references-to-elements), it isn't a [JavaScript interop](xref:client-side/blazor/javascript-interop) feature. Component references aren't passed to JavaScript code; they're only used in .NET code.
 
 > [!NOTE]
 > Do **not** use component references to mutate the state of child components. Instead, always use normal declarative parameters to pass data to child components. This causes child components to rerender at the correct times automatically.

docs/routing.md

@@ -38,7 +38,7 @@ Multiple route templates can be applied to a component. In the [sample app](http
 [!code-cshtml[](common/samples/2.x/BlazorSample/Pages/BlazorRoute.cshtml?start=1&end=4)]
 
 > [!IMPORTANT]
-> To generate routes properly, the app must include a `<base>` tag in its *wwwroot/index.html* file with the app base path specified in the `href` attribute (`<base href="/" />`). For more information, see [Host and deploy: App base path](xref:client-side/blazor/routing#app-base-path).
+> To generate routes properly, the app must include a `<base>` tag in its *wwwroot/index.html* file with the app base path specified in the `href` attribute (`<base href="/" />`). For more information, see [Host and deploy: App base path](xref:client-side/blazor/host-and-deploy/index#app-base-path).
 
 ## Route parameters