docs: simplified notes on subnets

Author: JTorreG

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

@@ -58,16 +58,15 @@ You can start the NGINXaaS deployment process by visiting the [Create NGINXaaS](
    | Apply default NGINX configuration | Confirm that you want your NGINXaaS deployment to be bootstrapped with a default NGINX configuration and a browsable splash page. |
    {{</bootstrap-table>}}
 
-   #### **Notes on subnets:**
+   #### Notes on subnets:
 
    - The minimum subnet size for NGINXaaS is `/27` and is enough for a single NGINXaaS deployment even at large scales.
-   - You can use an existing subnet; make sure that the subnet is delegated to `NGINX.NGINXPLUS/nginxDeployments` before creating a deployment in it. To delegate a subnet to an Azure service, see [Delegate a subnet to an Azure service](https://learn.microsoft.com/en-us/azure/virtual-network/manage-subnet-delegation?source=recommendations#delegate-a-subnet-to-an-azure-service).
-   - The subnet can contain other resources; ensure the subnet size is adequate to scale the NGINXaaS deployment.
-   - You can deploy more than one NGINXaaS in the same subnet, however, every deployment in the subnet will share the subnet IP address space, so ensure the subnet is adequately sized to scale the deployments. If you have more than one NGINXaaS deployment or other resources, a larger subnet, for example, a `/24` is recommended.
-   - You can change the virtual network or subnet for an existing NGINXaaS deployment. If the existing NGINXaaS deployment is using a public IP address, you can change the backend virtual network or subnet. Please make sure that the subnet is delegated to `NGINX.NGINXPLUS/nginxDeployments` before creating a deployment in it.
-   - If your DNS nameservers are configured in the same VNet as your deployment, then you can use those DNS nameservers to resolve the hostname of the upstream servers referenced in your NGINX configuration.
+   - You can use an existing subnet; make sure that the subnet is delegated to `NGINX.NGINXPLUS/nginxDeployments` before creating a deployment in it. The subnet can contain other resources.
+   - You can deploy more than one NGINXaaS in the same subnet. Every deployment in the subnet will share the subnet IP address space. A larger subnet, for example, a `/24` is recommended.
    - 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>Example of using the resolver directive</summary>
       For example,
 
       ```nginx
@@ -83,6 +82,7 @@ You can start the NGINXaaS deployment process by visiting the [Create NGINXaaS](
          }
       }
       ```
+      </details>
 
 
 1. Next, select **Tags**.