Merge pull request #236065 from domainname/assign-public-endpoint

fix instructions to assign a public endpoint to an application

Author: prmerger-automator[bot]

articles/spring-apps/how-to-launch-from-source.md

@@ -29,7 +29,7 @@ This quickstart explains how to:
 > * Set a configuration server for an instance
 > * Build an application locally
 > * Deploy each application
-> * Assign a public endpoint for your application
+> * Assign a public endpoint for an application
 
 ## Prerequisites
 
@@ -146,12 +146,12 @@ az spring app show-deploy-log --name <app-name>
 > [!NOTE]
 > The kpack logs will only show the latest deployment if that deployment was built from source using kpack.
 
-## Assign a public endpoint to gateway
+## Assign a public endpoint to an application
 
-1. Open the **Application Dashboard** page.
-2. Select the `gateway` application to show the **Application Details** page.
-3. Select **Assign endpoint** to assign a public endpoint to gateway. This can take a few minutes.
-4. Enter the assigned public IP into your browser to view your running application.
+1. Open the **Apps** pane to view apps for your service instance.
+2. Select an application to view its **Overview** page.
+3. Select **Assign endpoint** to assign a public endpoint to the application. This process can take a few minutes.
+4. Copy the URL from the **Overview** page and then paste it into your browser to view your running application.
 
 > [!div class="nextstepaction"]
 > [I ran into an issue](https://www.research.net/r/javae2e?tutorial=asc-source-quickstart&step=public-endpoint)
@@ -166,7 +166,7 @@ In this quickstart, you learned how to:
 > * Build an application locally
 > * Deploy each application
 > * Edit environment variables for applications
-> * Assign public IP for your application gateway
+> * Assign a public endpoint to an application
 
 > [!div class="nextstepaction"]
 > [Quickstart: Monitoring Azure Spring Apps with logs, metrics, and tracing](./quickstart-logs-metrics-tracing.md)