updates

Author: craigshoemaker

articles/static-web-apps/deploy-nextjs-hybrid.md

@@ -325,7 +325,7 @@ Next, configure the `build` command in the `package.json` file in order to copy
 }
 ```
 
-## Configure your Next.js routing and middleware for deployment to Azure Static Web Apps
+## Configure routing and middleware for deployment
 
 Your Next.js project can be configured to have custom handling of routes with redirects, rewrites, and middleware. These handlers are commonly used for authentication, personalization, routing, and internationalization. Custom handling affects the default routing of your Next.js site and the configuration must be compatible with hosting on Static Web Apps.
 

includes/static-web-apps/static-web-apps-nextjs-backends.md

@@ -8,12 +8,12 @@ ms.author: cshoe
 
 A managed backed is automatically available for every hybrid Next.js deployment. However, you can fine tune performance and take more control of the backend by assigning a custom backend to your site. The following steps show you how to associate a custom backend to your site.
 
-When you link the backend resource to your Next.js app, server-side requests are served from the backend server.
-
 1. Go to your static web app in the Azure portal.
 
 1. Select **Settings** and then **APIs** from the side menu.
 
+1. Under the *Backend Resource Name*, select the link labeled **(managed)**.
+
 1. Select **Configure linked backend**.
 
 1. Either create a new App Service Plan or select an existing App Service Plan.