Merge pull request #127221 from changeworld/patch-9

Fix typo: publically -> publicly

Author: v-dirichards

articles/spring-apps/basic-standard/concept-manage-monitor-app-spring-boot-actuator.md

@@ -69,7 +69,7 @@ In the Enterprise plan, there are two ways to secure the access:
 
 - You can disable the public endpoint of apps and configure a routing rule in VMware Spring Cloud Gateway to disable actuator access from the public. For more information, see [Configure VMware Spring Cloud Gateway](../enterprise/how-to-configure-enterprise-spring-cloud-gateway.md).
 
-- You can configure the actuator to listen on a different HTTP port from the main application. In a standalone application, the actuator HTTP port defaults to the same as the main HTTP port. For the application to listen on a different port, set the `management.server.port` property. The Application Live View is unable to automatically detect this port change, so you also need to configure the property on an Azure Spring Apps deployment. Then, the actuator isn't publically accessible, but the Application Live View can read from the actuator endpoint via another port. For more information, see [Use Application Live View with the Azure Spring Apps Enterprise plan](../enterprise/how-to-use-application-live-view.md).
+- You can configure the actuator to listen on a different HTTP port from the main application. In a standalone application, the actuator HTTP port defaults to the same as the main HTTP port. For the application to listen on a different port, set the `management.server.port` property. The Application Live View is unable to automatically detect this port change, so you also need to configure the property on an Azure Spring Apps deployment. Then, the actuator isn't publicly accessible, but the Application Live View can read from the actuator endpoint via another port. For more information, see [Use Application Live View with the Azure Spring Apps Enterprise plan](../enterprise/how-to-use-application-live-view.md).
 
 ## Next steps