Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into afd-faq

Author: halkazwini

articles/app-service/configure-language-python.md

@@ -7,7 +7,7 @@ ms.reviewer: astay
 ms.author: msangapu
 author: msangapu-msft
 ms.devlang: python
-ms.custom: mvc, devx-track-python, devx-track-azurecli, mode-other, py-fresh-zinc, linux-related-content
+ms.custom: mvc, devx-track-python, devx-track-azurecli, mode-other, py-fresh-zinc, linux-related-content, innovation-engine
 adobe-target: true
 ---
 

articles/app-service/media/routine-maintenance/routine-maintenance-first-page.png

@@ -24,7 +24,7 @@ Like personal computers, mobile phones, and other devices, machines in the cloud
 
 Because a typical cloud solution consists of multiple applications, databases, storage accounts, functions, and other resources, parts of your solutions can undergo maintenance at different times. Some of this coordination is related to geography, region, datacenters, and availability zones. It can also be due to the cloud, where not everything is touched simultaneously. For more information, see [Safe deployment practices](/devops/operate/safe-deployment-practices).
 
-The following screenshot shows an example of a maintenance event.
+The following screenshot shows an example of a maintenance event:
 
 :::image type="content" source="./media/routine-maintenance/routine-maintenance.png" alt-text="Screenshot of a maintenance event in the Azure portal.":::
 
@@ -34,6 +34,23 @@ In order from top to bottom, the example shows:
 - Affected regions and subscriptions.
 - The expected maintenance window.
 
+The following screenshots show additional information available through the Impacted Resources dropdown:
+
+:::image type="content" source="./media/routine-maintenance/routine-maintenance-first-page.png" alt-text="Screenshot of the Impacted Resources blade in the Azure portal.":::
+
+In order from left to right, the example shows:
+
+- Selecting the "Impacted Resources" dropdown.
+- The "More info" option.
+
+:::image type="content" source="./media/routine-maintenance/routine-maintenance-more.png" alt-text="Screenshot of more info for a maintenance event in the Azure portal.":::
+
+This example shows:
+
+- The state of the maintenance, which can be pending, started, or completed.
+- Once maintenance starts, timestamps can be viewed under "More info."
+
+
 ## Frequently asked questions
 
 ### Why is the maintenance taking so long?

articles/app-service/media/routine-maintenance/routine-maintenance-more.png

@@ -5,7 +5,7 @@ services: application-gateway
 author: greg-lindsay
 ms.service: azure-appgw-for-containers
 ms.topic: how-to
-ms.date: 3/7/2025
+ms.date: 3/21/2025
 ms.author: greglin
 ---
 
@@ -15,7 +15,7 @@ This guide demonstrates how to use cert-manager to automatically issue and renew
 
 For the purposes of this example, we have cert-manager configure certificates issued from Let's Encrypt to demonstrate an end-to-end deployment, where Application Gateway for Containers is providing TLS offloading.
 
-![A figure showing cert-manager retrieving a certificate from Let's Encrypt and storing it into Kubernetes' secret store for TLS with Application Gateway for Containers.](./media/how-to-cert-manager-lets-encrypt-gateway-api/how-to-cert-manager-lets-encrypt-gateway-api.svg)
+[![A diagram showing cert-manager retrieving a certificate from Let's Encrypt and storing it into Kubernetes' secret store for TLS with Application Gateway for Containers.](./media/how-to-cert-manager-lets-encrypt-gateway-api/how-to-cert-manager-lets-encrypt-gateway-api.svg) ](./media/how-to-cert-manager-lets-encrypt-gateway-api/how-to-cert-manager-lets-encrypt-gateway-api.svg#lightbox)
 
 For certificates to be issued by Let's Encrypt, a challenge is required by the authority to validate domain ownership. This validation happens by allowing cert-manager to create a pod and HTTPRoute resource that exposes an endpoint during certificate issuance, proving your ownership of the domain name.
 
@@ -437,7 +437,7 @@ Now we're ready to send some traffic to our sample application, via the hostname
 curl https://contoso.com/ -v 2>&1 | grep issuer
 ```
 
-Upon result, you should see
+You should see the following output:
 
 `*  issuer: C=US; O=Let's Encrypt; CN=R10`