fix: dropdowns rendered as literal on Plus + NGINXaaS docs (#1378)

Author: lamATnginx

content/includes/nginx-plus/install/pin-to-version/pin-debian-ubuntu-R32.md

@@ -8,16 +8,14 @@ To pin NGINX Plus to a specific version (for example, R33):
 1. Update the repository base URL to the desired version:
 
    - **For Ubuntu**:
-
-      ```shell
-      https://pkgs.nginx.com/plus/R33/ubuntu
-      ```
+     ```shell
+     https://pkgs.nginx.com/plus/R33/ubuntu
+     ```
 
    - **For Debian**:
-
-      ```shell
-      https://pkgs.nginx.com/plus/R33/debian
-      ```
+     ```shell
+     https://pkgs.nginx.com/plus/R33/debian
+     ```
 
 3. Save the changes and exit.
 

content/nginx/admin-guide/installing-nginx/installing-nginx-plus.md

@@ -98,11 +98,7 @@ This article explains how to install NGINX Plus on different operating systems,
     sudo wget -P /etc/yum.repos.d https://cs.nginx.com/static/files/nginx-plus-8.repo
     ```
 
-    {{< details summary="Pin NGINX Plus to a specific version" >}}
-    
-    {{< call-out "note">}}
-        {{< include "nginx-plus/install/pin-to-version/pin-rhel8-R32.md" >}}
-    {{< /call-out >}}
+    {{< details summary="Pin NGINX Plus to a specific version" >}}{{< call-out "note">}}{{< include "nginx-plus/install/pin-to-version/pin-rhel8-R32.md" >}}{{< /call-out >}}
 
     {{< /details >}}
 
@@ -138,13 +134,7 @@ This article explains how to install NGINX Plus on different operating systems,
     sudo wget -P /etc/yum.repos.d https://cs.nginx.com/static/files/plus-9.repo
     ```
 
-    {{< details summary="Pin NGINX Plus to a specific version" >}}
-    
-    {{< call-out "note">}}
-        {{< include "nginx-plus/install/pin-to-version/pin-rhel9-R32.md" >}}   
-    {{< /call-out >}}
-    
-    {{< /details >}}
+    {{< details summary="Pin NGINX Plus to a specific version" >}}{{< call-out "note">}}{{< include "nginx-plus/install/pin-to-version/pin-rhel9-R32.md" >}}{{< /call-out >}}{{< /details >}}
 
 1. {{< include "nginx-plus/install/install-nginx-plus-package-dnf.md" >}}
 
@@ -222,13 +212,7 @@ NGINX Plus can be installed on the following versions of Debian or Ubuntu:
         | sudo tee /etc/apt/sources.list.d/nginx-plus.list
         ```
 
-    {{< details summary="Pin NGINX Plus to a specific version" >}}
-    
-    {{< call-out "note">}}
-        {{< include "nginx-plus/install/pin-to-version/pin-debian-ubuntu-R32.md" >}}
-    {{< /call-out >}}
-    
-    {{< /details >}}
+    {{< details summary="Pin NGINX Plus to a specific version" >}}{{< call-out "note">}}{{< include "nginx-plus/install/pin-to-version/pin-debian-ubuntu-R32.md" >}}{{< /call-out >}}{{< /details >}}
 
 1. Download the **nginx-plus** apt configuration to **/etc/apt/apt.conf.d**:
 

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

@@ -65,22 +65,23 @@ You can start the NGINXaaS deployment process by visiting the [Create NGINXaaS](
    - If you plan on using an IPv6 address on the frontend, make sure the subnet is dual-stack, i.e., the subnet has both IPv4 and IPv6 address spaces. Attempting to use a subnet that is not dual-stack will cause deployment creation to fail.
    - Changes to a virtual network's DNS settings will not be applied automatically to your NGINXaaS deployment. To ensure DNS settings are applied, you must add any custom DNS servers to the VNET's DNS settings before creating an NGINXaaS deployment. As a workaround for existing deployments, we recommend using the [`resolver` directive](https://nginx.org/en/docs/http/ngx_http_core_module.html#resolver) to explicitly specify your name server(s) and the [`resolve` parameter](https://nginx.org/en/docs/http/ngx_http_upstream_module.html#resolve) to automatically re-resolve the domain name of the server without restarting NGINX.
 
-      {{< details summary="Resolver directive example" >}}
-
-      ```nginx
-      resolver 10.0.0.2 valid=10s;
-      upstream backends {
-         zone backends 64k;
-         server backends.example.com:8080 resolve;
-      }
-
-      server {
-         location / {
-            proxy_pass http://backends;
-         }
+   {{<details summary="Resolver directive example">}}
+
+   ```nginx
+   resolver 10.0.0.2 valid=10s;
+   upstream backends {
+      zone backends 64k;
+      server backends.example.com:8080 resolve;
+   }
+
+   server {
+      location / {
+         proxy_pass http://backends;
       }
-      ```
-      {{< /details >}}
+   }
+   ```
+      
+   {{</details>}}
 
 
 1. Next, select **Tags**.