Merge pull request #31538 from codyhoag/wind-updates-2

BZ#1943587 WINC minor updates and typos

Author: codyhoag

modules/collecting-kube-node-logs-windows.adoc

@@ -5,7 +5,7 @@
 [id="collecting-kube-node-logs-windows_{context}"]
 = Collecting Kubernetes node logs for Windows containers
 
-Windows container logging works differently from Linux container logging; the Kubernetes node logs for Windows workloads are streamed to the `C:\k\logs` directory by default. Therefore, you must gather the Windows node logs from that directory.
+Windows container logging works differently than Linux container logging; the Kubernetes node logs for Windows workloads are streamed to the `C:\var\logs` directory by default. Therefore, you must gather the Windows node logs from that directory.
 
 .Prerequisites
 
@@ -14,7 +14,7 @@ Windows container logging works differently from Linux container logging; the Ku
 
 .Procedure
 
-. To view the logs under all directories in `C:\k\logs`, run the following command:
+. To view the logs under all directories in `C:\var\logs`, run the following command:
 +
 [source,terminal]
 ----

modules/creating-the-vsphere-windows-vm-golden-image.adoc

@@ -16,7 +16,7 @@ Create a vSphere Windows virtual machine (VM) golden image.
 
 . Create the VM from an updated version of the Windows Server 1909 VM image that includes the link:https://support.microsoft.com/en-us/help/4565351/windows-10-update-kb4565351[Microsoft patch KB4565351]. This patch is required to set the VXLAN UDP port, which is required for clusters installed on vSphere. This patch is not available for the `Windows Server 2019` VM image.
 
-. Create the `C:\Users\Administrator.ssh\authorized_keys` file in the Windows VM containing the public key that corresponds to the private key that resides in the secret you created in the `openshift-windows-machine-config-operator` namespace. The private key of the secret was created when first installing the Windows Machine Config Operator (WMCO) to give {product-title} access to Windows VMs. The `authorized_keys` file is used to configure SSH in the Windows VM.
+. Create the `C:\Users\Administrator\.ssh\authorized_keys` file in the Windows VM containing the public key that corresponds to the private key that resides in the secret you created in the `openshift-windows-machine-config-operator` namespace. The private key of the secret was created when first installing the Windows Machine Config Operator (WMCO) to give {product-title} access to Windows VMs. The `authorized_keys` file is used to configure SSH in the Windows VM.
 
 . Configure SSH on the Windows VM by running the following Powershell script:
 +
@@ -83,7 +83,7 @@ An example `unattend.xml` is provided, which maintains all the changes needed fo
 <!--A sample unattend.xml which helps in setting admin password and running scripts on first boot-->
 <unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="specialize">
-      <component xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http:// www.w3.org/2001/XMLSchema-instance" name="Microsoft-Windows-International-Core" processorArchitecture="am d64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
+      <component xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http:// www.w3.org/2001/XMLSchema-instance" name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
          <InputLocale>0409:00000409</InputLocale>
          <SystemLocale>en-US</SystemLocale>
          <UILanguage>en-US</UILanguage>

modules/enabling-internal-api-server-vsphere.adoc

@@ -5,7 +5,7 @@
 [id="enabling-internal-api-server-vsphere_{context}"]
 = Enabling communication with the internal API server for the WMCO on vSphere
 
-The Windows Machine Config Operator (WMCO) downloads the Ignition config files from the internal API server endpoint. You must enable communication with the internal API server so that your Windows virtual machine (VM) can download the Ignition config files, and the kubelet on the configured VM can communicate with the internal API server.
+The Windows Machine Config Operator (WMCO) downloads the Ignition config files from the internal API server endpoint. You must enable communication with the internal API server so that your Windows virtual machine (VM) can download the Ignition config files, and the kubelet on the configured VM can only communicate with the internal API server.
 
 .Prerequisites