diff --git a/aspnetcore/blazor/progressive-web-app.md b/aspnetcore/blazor/progressive-web-app.md
index e2fc6ca8ce92..5edac0eced1f 100644
--- a/aspnetcore/blazor/progressive-web-app.md
+++ b/aspnetcore/blazor/progressive-web-app.md
@@ -322,10 +322,16 @@ The `AssetUrl` metadata specifies the base-relative URL that the browser should
 
 Like any other PWA, a Blazor WebAssembly PWA can receive push notifications from a backend server. The server can send push notifications at any time, even when the user isn't actively using the app. For example, push notifications can be sent when a different user performs a relevant action.
 
+<!-- UPDATE 10.0 - REMOVING FOR NOW. The content at the destination was pulled
+                   on https://github.com/dotnet-presentations/blazor-workshop/pull/368.
+                   I'll converse with DR about what else we can point to for this.
+                   
 The mechanism for sending a push notification is entirely independent of Blazor WebAssembly, since it's implemented by the backend server which can use any technology. If you want to send push notifications from an ASP.NET Core server, consider [using a technique similar to the approach taken in the Blazing Pizza workshop](https://github.com/dotnet-presentations/blazor-workshop/blob/master/docs/09-progressive-web-app.md#sending-push-notifications).
 
 The mechanism for receiving and displaying a push notification on the client is also independent of Blazor WebAssembly, since it's implemented in the service worker JavaScript file. For an example, see [the approach used in the Blazing Pizza workshop](https://github.com/dotnet-presentations/blazor-workshop/blob/master/docs/09-progressive-web-app.md#displaying-notifications).
 
+-->
+
 ## Caveats for offline PWAs
 
 Not all apps should attempt to support offline use. Offline support adds significant complexity, while not always being relevant for the use cases required.
diff --git a/aspnetcore/host-and-deploy/health-checks.md b/aspnetcore/host-and-deploy/health-checks.md
index de8360907ffe..995fbf571a2e 100644
--- a/aspnetcore/host-and-deploy/health-checks.md
+++ b/aspnetcore/host-and-deploy/health-checks.md
@@ -43,7 +43,7 @@ The following example creates a health check endpoint at `/healthz`:
 [Docker](xref:host-and-deploy/docker/index) offers a built-in `HEALTHCHECK` directive that can be used to check the status of an app that uses the basic health check configuration:
 
 ```dockerfile
-HEALTHCHECK CMD curl --fail http://localhost:5000/healthz || exit
+HEALTHCHECK CMD curl --fail http://localhost:5000/healthz || exit 1
 ```
 
 The preceding example uses `curl` to make an HTTP request to the health check endpoint at `/healthz`. `curl` isn't included in the .NET Linux container images, but it can be added by installing the required package in the Dockerfile. Containers that use images based on Alpine Linux can use the included `wget` in place of `curl`.