Update vnet-custom.md

- Removing the Additional Resources section. Private endpoints are not supported, In contrast with internal Environments, setting up DNS for external Environments is not required, and having this bullet point might cause confusion.
- Moved the caution about the clean-up command to the azure-cli zone because it is only applicable to the commands in the azure-cli zone.

Author: gabesmsft

articles/container-apps/vnet-custom.md

@@ -335,11 +335,11 @@ You must either provide values for all three of these properties, or none of the
 
 If you're not going to continue to use this application, you can delete the Azure Container Apps instance and all the associated services by removing the **my-container-apps** resource group.  Deleting this resource group will also delete the resource group automatically created by the Container Apps service containing the custom network components.
 
+::: zone pivot="azure-cli"
+
 >[!CAUTION]
 > The following command deletes the specified resource group and all resources contained within it. If resources outside the scope of this guide exist in the specified resource group, they will also be deleted.
 
-::: zone pivot="azure-cli"
-
 # [Bash](#tab/bash)
 
 ```azurecli
@@ -356,11 +356,6 @@ Remove-AzResourceGroup -Name $ResourceGroupName -Force
 
 ::: zone-end
 
-## Additional resources
-
-- For more information about configuring your private endpoints, see [What is Azure Private Endpoint](../private-link/private-endpoint-overview.md).
-- To set up DNS name resolution for internal services, you must [set up your own DNS server](../dns/index.yml).
-
 ## Next steps
 
 > [!div class="nextstepaction"]