Fixed issues raised in MicrosoftDocs/azure-docs-pr#287558 (comment)

yousefi-msft · yousefi-msft · commit 22503fa92d21 · 2024-09-30T20:39:46.000-04:00
diff --git a/articles/modeling-simulation-workbench/resources-troubleshoot.md b/articles/modeling-simulation-workbench/resources-troubleshoot.md
@@ -14,7 +14,7 @@ ms.date: 07/19/2023
 
 This troubleshooting guide contains general troubleshooting steps and information for Azure Modeling and Simulation Workbench. The content is organized by topic type.
 
-Additional troubleshooting steps for transient issues can be found on the [Known Issues] page.
+Additional troubleshooting steps for transient issues can be found on the [Known Issues](./troubleshoot-known-issues.md) page.
 
 ## Remote desktop troubleshooting
 
diff --git a/articles/modeling-simulation-workbench/troubleshoot-known-issues.md b/articles/modeling-simulation-workbench/troubleshoot-known-issues.md
@@ -1,5 +1,5 @@
 ---
-title: Known issues for Modeling and Simulation Workbench
+title: Known issues for Azure Modeling and Simulation Workbench
 description: "Troubleshooting guide for known issues on Azure Modeling and Simulation Workbench."
 author: yousefi-msft
 ms.author: yousefi
@@ -85,7 +85,7 @@ While uploading files into a chamber, you might see a file that isn't the expect
 
 The file isn't corrupt or truncated, but still uploading. The data pipeline isn't a single stage and files placed in the upload pipeline don't appear instantaneously in the */mount/datapipeline/datain* directory and are likely still completing. Check back later and verify the length or hash.
 
-## Azure VMs located in the same region as a workbench can't access a public ip connector
+## Azure VMs located in the same region as a workbench can't access a public IP connector
 
 Resources deployed outside of a workbench, in particular virtual machines (VM), can't access a chamber through a public IP connector if located in the same region. A VM deployed in the same region or even the same resource group as a workbench isn't able to connect to the chamber's connector. The VM's public facing IP address is on the allowlist. A locally installed version of AzCopy is unable to access the chamber's data pipeline. Errors include timeouts or not authorized.
 
