docs: convert markdown images to shortcode images

Author: JTorreG

content/nginxaas-azure/getting-started/create-deployment/deploy-azure-portal.md

@@ -72,7 +72,7 @@ You can start the NGINXaaS deployment process by visiting the [Create NGINXaaS](
 
 1. After the deployment finishes, select the NGINX deployment from the list (with "Type: NGINXaaS") to view information about the deployed resource.
 
-   ![Resource Deployment Completed page showing the available deployments and the new NGINXaaS type deployment in the Deployment details section.](nginxaas-azure/deployment-complete.png)
+   {{< img src="nginxaas-azure/deployment-complete.png" alt="Resource Deployment Completed page showing the available deployments and the new NGINXaaS type deployment in the Deployment details section." >}}
 
 
 ## Test your deployment
@@ -81,7 +81,7 @@ You can start the NGINXaaS deployment process by visiting the [Create NGINXaaS](
 
    {{<note>}}You will not see the default NGINX welcome screen if you unchecked "Apply default NGINX configuration" in the [Networking Tab screen]({{< relref "create-deployment.md#networking-tab" >}}) above. You can proceed with providing your own NGINX configuration as outlined in the [NGINX configuration]({{< relref "nginx-configuration.md#networking-tab" >}}) section.{{</note>}}
 
-   ![NGINXaaS Overview page showing the IP address of the deployment in the Essentials section.](nginxaas-azure/test-deployment.png)
+   {{< img src="nginxaas-azure/test-deployment.png" alt="NGINXaaS Overview page showing the IP address of the deployment in the Essentials section." >}}
 
 
 ## What's next

content/nginxaas-azure/getting-started/nginx-configuration/nginx-configuration-portal.md

@@ -54,7 +54,7 @@ NGINX configuration is validated real-time to check for syntax and compatibility
 
 For example, if you create/update an NGINX config with a particular directive that is not allowed, the service will analyse your NGINX config and provide real-time feedback.
 
-![NGINX Configuration validation error](nginxaas-azure/validation-error.png)
+{{< img src="nginxaas-azure/validation-error.png" alt="NGINX Configuration validation error" >}}
 
 
 The editing experience consists of a single view for both editing and validation

content/nginxaas-azure/getting-started/ssl-tls-certificates/overview.md

@@ -58,7 +58,7 @@ To view the status of your SSL/TLS certificates, [enable monitoring]({{< relref
 
    {{</bootstrap-table>}}
 
-   ![Interface screenshot showing the Azure metric nginxaas.certificates](nginxaas-azure/azure-metrics-nginxaas.certificates.png)
+   {{< img src="nginxaas-azure/azure-metrics-nginxaas.certificates.png" alt="Interface screenshot showing the Azure metric nginxaas.certificates" >}}
 
 ## Common certificate errors
 

content/nginxaas-azure/monitoring/configure-alerts.md

@@ -39,14 +39,14 @@ This guide explains how to create and configure metrics-based alerts for your NG
 
 5. In the **Conditions** tab, select a **Signal name**, for example, "nginx.http.request.count".
 
-   ![Screenshot of the Conditions tab showing how to select a Signal name from the list](nginxaas-azure/alert-select-signal.png)
+   {{< img src="nginxaas-azure/alert-select-signal.png" alt="Screenshot of the Conditions tab showing how to select a Signal name from the list" >}}
 
 6. Define the **alert logic** such as:
 
    - Set the threshold and average as per your requirements.
    - Set the frequency to evaluate alerts as per your requirements.
 
-   ![Screenshot of the alert logic page showing how to set the threshold and frequency](nginxaas-azure/alert-logic.png)
+   {{< img src="nginxaas-azure/alert-logic.png" alt="Screenshot of the alert logic page showing how to set the threshold and frequency" >}}
 
 7. Define the **actions**:
 

content/nginxaas-azure/monitoring/enable-logging/logging-using-portal.md

@@ -43,7 +43,7 @@ Enabling logs using the **NGINX Logs** blade on your NGINXaaS deployment is now
 
 1. Select preferred **Destination details**.
 
-   ![Screenshot of the Diagnostic Settings configuration page](nginxaas-azure/diagnostic-settings.png)
+   {{< img src="nginxaas-azure/diagnostic-settings.png" alt="Screenshot of the Diagnostic Settings configuration page" >}}
 
 For more information about diagnostic settings destinations, please see the [Diagnostic Settings Destinations](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/diagnostic-settings#destinations) documentation.
 

content/nginxaas-azure/overview/overview.md

@@ -39,7 +39,7 @@ NGINXaaS for Azure is supported in the following regions:
 
 ## NGINXaaS architecture
 
-![The diagram illustrates the architecture of F5 NGINXaaS for Azure within a Microsoft Azure environment. It shows admins using Azure API/SDK, Azure Portal, Azure CLI, and Terraform to interact with the NGINX Plus component in the IaaS layer for edge routing. The diagram also depicts subnet delegation from the NGINX Plus component to a customer subscription, which includes Azure Key Vault, Azure Monitor, other Azure services, and multiple application servers (App Server 1, App Server 2, App Server N)](nginxaas-azure/n4a-architecture.png)
+{{< img src="nginxaas-azure/n4a-architecture.png" alt="The diagram illustrates the architecture of F5 NGINXaaS for Azure within a Microsoft Azure environment. It shows admins using Azure API/SDK, Azure Portal, Azure CLI, and Terraform to interact with the NGINX Plus component in the IaaS layer for edge routing. The diagram also depicts subnet delegation from the NGINX Plus component to a customer subscription, which includes Azure Key Vault, Azure Monitor, other Azure services, and multiple application servers (App Server 1, App Server 2, App Server N)." >}}
 
 - Azure management tools (API, CLI, portal, terraform) work with NGINXaaS to create, update, and delete deployments
 - Each NGINXaaS deployment has dedicated network and compute resources. There is no possibility of [noisy neighbor problems](https://learn.microsoft.com/en-us/azure/architecture/antipatterns/noisy-neighbor/noisy-neighbor) or data leakage between deployments
@@ -57,7 +57,7 @@ With the Standard Plan, NGINXaaS uses the following redundancy features to keep
 
 ### Data plane traffic
 
-![The diagram illustrates the architecture of F5 NGINXaaS for Azure, showing end users accessing a public IP that routes through a network security group within a customer's Azure subscription. This leads to a delegated subnet in a virtual network, which connects to a zone-redundant load balancer within the NGINXaaS subscription. The load balancer distributes traffic across NGINX Plus instances in multiple availability zones, ensuring scalability and redundancy](nginxaas-azure/n4a-data-plane-architecture.svg)
+{{< img src="nginxaas-azure/n4a-data-plane-architecture.svg" alt="The diagram illustrates the architecture of F5 NGINXaaS for Azure, showing end users accessing a public IP that routes through a network security group within a customer's Azure subscription. This leads to a delegated subnet in a virtual network, which connects to a zone-redundant load balancer within the NGINXaaS subscription. The load balancer distributes traffic across NGINX Plus instances in multiple availability zones, ensuring scalability and redundancy." >}}
 
 NGINXaaS uses new Azure networking capabilities to keep end-user traffic private. Each NGINX Plus instance passes traffic to  downstream services using an elastic network card (NIC) that exists inside your subscription. These NICs are injected into a delegated virtual network. A network security group controls traffic to your NGINX Plus instances.
 

content/nginxaas-azure/quickstart/security-controls/auth-basic.md

@@ -15,7 +15,7 @@ For more information on configuring HTTP Basic Authentication please refer to th
 
 F5 NGINX as a Service for Azure (NGINXaaS) accepts a file containing usernames and passwords using any of the password types specified in the [NGINX documentation](https://nginx.org/en/docs/http/ngx_http_auth_basic_module.html#auth_basic_user_file). The password file can be uploaded as a "protected file" when creating or updating your NGINX configuration to protect the file's contents from being read. The password file can alternatively be uploaded as a regular file.
 
-![Screenshot of the Azure portal showing the password file upload](nginxaas-azure/auth-basic-htpasswd.png)
+{{< img src="nginxaas-azure/auth-basic-htpasswd.png" alt="Screenshot of the Azure portal showing the password file upload" >}}
 
 ## Configuring NGINX Plus for HTTP basic authentication
 

content/nginxaas-azure/quickstart/security-controls/securing-upstream-traffic.md

@@ -52,7 +52,7 @@ If your configuration is using the [njs module]({{< relref "/nginxaas-azure/quic
 
 Toggle `yes` to include the CA file as proctectd file when using Azure Portal as show below:
 
-![Screenshot of the Azure portal showing the toggle for protected files](nginxaas-azure/add-ca-as-protected-file.png)
+{{< img src="nginxaas-azure/add-ca-as-protected-file.png" alt="Screenshot of the Azure portal showing the toggle for protected files" >}}
 
 ### Configuring upstreams
 

content/nginxaas-azure/troubleshooting/troubleshooting.md

@@ -17,15 +17,15 @@ To contact support about F5 NGINX as a Service for Azure (NGINXaaS):
 
 3. Select **Raise a Support ticket**.
 
-   ![Screenshot of the Azure portal showing the Raise support ticket button](nginxaas-azure/raise-ticket.png)
+   {{< img src="nginxaas-azure/raise-ticket.png" alt="Screenshot of the Azure portal showing the Raise support ticket button" >}}
 
 4. You will be redirected to **MyF5** to create a new case. Log in to MyF5 with your F5 account.
 
 {{< note >}}If you can't complete a deployment successfully, the "New support request" option won't be available on the left-hand navigation menu. To raise a support ticket, go to the [MyF5 portal](https://my.f5.com). {{< /note >}}
 
 5. Go to the **Case Management** section and select **Create new case**.
 
-   ![Screenshot of the MyF5 portal showing the Create new case button](nginxaas-azure/new-case.png)
+   {{< img src="nginxaas-azure/new-case.png" alt="Screenshot of the MyF5 portal showing the Create new case button" >}}
 
 6. Select **NGINXaaS** in the Product dropdown.
 
@@ -37,7 +37,7 @@ To contact support about F5 NGINX as a Service for Azure (NGINXaaS):
 - Date and time of the issue
 - Resource ID
 
-![Screenshot of the Azure portal showing the Properties section](nginxaas-azure/properties.png)
+{{< img src="nginxaas-azure/properties.png" alt="Screenshot of the Azure portal showing the Properties section" >}}
 
 8. Complete the **Additional information** and **Contact details** sections of your case and select **Submit**.