Merge branch 'MicrosoftDocs:main' into Spelling-Wave-12

Author: ArieHein

articles/azure-vmware/faq.yml

@@ -275,8 +275,8 @@ sections:
   - name: Hosts, clusters, and private clouds
     questions:
 
-      - question: Is there more than one type of host available?
-        answer:  No. There's only one type available.
+      - question: Is there more than one type of host available per private cloud? Is it possible to combine different host types in a cluster or private cloud?
+        answer:  With the exception of AV64 cluster requiring a separate 3-node cluster minimum of AV36, AV36P, or AV52, you cannot combine different host types in a private cloud. In all scenarios, clusters require the same host type. Multiple clusters can be deployed within a single private cloud. All hosts must be the same type within a private cloud. If different host types are required to meet use case needs, additional private clouds must be deployed.
 
       - question: Do I use the same tools that I use now to manage private cloud resources?
         answer: Yes. The Azure portal is used for deployment and several management operations. vCenter Server and NSX Manager are used to manage vSphere and NSX resources.

articles/iot-edge/how-to-create-test-certificates.md

@@ -241,8 +241,8 @@ The **Edge CA** certificate is also responsible for creating certificates for mo
 
 3. This command creates several certificate and key files. The following certificate and key pair need to be copied over to an IoT Edge device and referenced in the config file:
 
-   * `certs\iot-edge-device-ca-<CA cert name>-full-chain.cert.pem`
-   * `private\iot-edge-device-ca-<CA cert name>.key.pem`
+   * `certs\iot-edge-device-<CA cert name>-full-chain.cert.pem`
+   * `private\iot-edge-device-<CA cert name>.key.pem`
 
 
 # [Linux](#tab/linux)

articles/service-bus-messaging/test-locally-with-service-bus-emulator.md

@@ -213,7 +213,7 @@ CONFIG_PATH="<Replace with path to Config.json file>"
 # SQL Edge EULA : https://go.microsoft.com/fwlink/?linkid=2139274
 ACCEPT_EULA="N"
 
-# 3. MSSQL_SA_PASSWORD to be filled by user as per policy : https://learn.microsoft.com/en-us/sql/relational-databases/security/strong-passwords?view=sql-server-linux-ver16 
+# 3. MSSQL_SA_PASSWORD to be filled by user as per policy : https://learn.microsoft.com/sql/relational-databases/security/strong-passwords?view=sql-server-linux-ver16 
 MSSQL_SA_PASSWORD: ""
 ```