Shortened titles

s-polly · s-polly · commit 1ae1d09bff34 · 2023-08-20T18:34:36.000-05:00
diff --git a/articles/machine-learning/known-issues/ki-applicaton-sharing-policy-not-supported.md b/articles/machine-learning/known-issues/ki-applicaton-sharing-policy-not-supported.md
@@ -10,7 +10,7 @@ ms.date: 08/14/2023
 ms.custom: known-issue
 ---
 
-# Known issue  - Compute Instance | Application Sharing Policy isn't supported
+# Known issue  - The ApplicationSharingPolicy property isn't supported for compute instances
 
 Configuring the `applicationSharingPolicy` property for a compute instance has no effect as that property isn't supported
 
diff --git a/articles/machine-learning/known-issues/ki-automl-error-generated-code.md b/articles/machine-learning/known-issues/ki-automl-error-generated-code.md
@@ -10,7 +10,7 @@ ms.date: 08/04/2023
 ms.custom: known-issue
 ---
 
-# Known issue  - AutoML | Error retrieving generated code FilesharePermissionFailure: Unable to copy files to fileshare because authorization failed.
+# Known issue  - FilesharePermissionFailure error retrieving generated code : Unable to copy files to fileshare because authorization failed.
 
 When a workspace has a public IP but the storage is private, then the workspace can't interact with the storage account directly. 
 
diff --git a/articles/machine-learning/known-issues/ki-compute-a10-sku-not-supported.md b/articles/machine-learning/known-issues/ki-compute-a10-sku-not-supported.md
@@ -10,7 +10,7 @@ ms.date: 08/14/2023
 ms.custom: known-issue
 ---
 
-# Known issue  - Compute | Provisioning error when creating a compute instance with A10 SKU
+# Known issue  - Provisioning error when creating a compute instance with A10 SKU
 
 [!INCLUDE [dev v2](../includes/machine-learning-dev-v2.md)]
 
diff --git a/articles/machine-learning/known-issues/ki-compute-idleshutdown-bicep.md b/articles/machine-learning/known-issues/ki-compute-idleshutdown-bicep.md
@@ -10,7 +10,7 @@ ms.date: 08/04/2023
 ms.custom: known-issue
 ---
 
-# Known issue  - Compute | Idleshutdown property in bicep template causes error
+# Known issue  - Idleshutdown property in Bicep template causes error
 
 When creating an Azure Machine Learning compute instance through Bicep, using the `idleTimeBeforeShutdown` property as described in the API reference [Microsoft.MachineLearningServices workspaces/computes API reference](/azure/templates/microsoft.machinelearningservices/workspaces/computes?pivots=deployment-language-bicep) results in an error.
 
diff --git a/articles/machine-learning/known-issues/ki-compute-slowness-terminal-mounted-path.md b/articles/machine-learning/known-issues/ki-compute-slowness-terminal-mounted-path.md
@@ -10,7 +10,7 @@ ms.date: 08/04/2023
 ms.custom: known-issue
 ---
 
-# Known issue  - Compute instance | Slowness in compute instance terminal from a mounted path
+# Known issue  - Slowness in compute instance terminal from a mounted path
 
 While using the compute instance terminal inside a mounted path of a data folder, any commands executed from the terminal result in slowness. This issue is restricted to the terminal; running the commands from SDK using a notebook works as expected.
 
diff --git a/articles/machine-learning/known-issues/ki-jupyter-r-kernel-not-starting.md b/articles/machine-learning/known-issues/ki-jupyter-r-kernel-not-starting.md
@@ -10,7 +10,7 @@ ms.date: 08/14/2023
 ms.custom: known-issue
 ---
 
-# Known issue  - Compute instance | Jupyter R Kernel doesn't start in new compute instance images 
+# Known issue  - Jupyter R Kernel doesn't start in new compute instance images 
 
 When trying to launch an R kernel in JupyterLab or a notebook in a new compute instance, the kernel fails to start with `Error: .onLoad failed in loadNamespace()`
 
diff --git a/articles/machine-learning/known-issues/ki-workspace-move-ci-same-name.md b/articles/machine-learning/known-issues/ki-workspace-move-ci-same-name.md
@@ -10,7 +10,7 @@ ms.date: 08/14/2023
 ms.custom: known-issue
 ---
 
-# Known issue  - Compute instance | Creating compute instance after a workspace move results in an Etag conflict error.
+# Known issue  - Creating compute instance after a workspace move results in an Etag conflict error.
 
 After a moving a workspace to a different subscription or resource group, creating a compute instance with the same name as a previous compute instance will fail with an Etag conflict error.
 
diff --git a/articles/machine-learning/known-issues/ki-workspace-storage-different-subscription.md b/articles/machine-learning/known-issues/ki-workspace-storage-different-subscription.md
@@ -10,7 +10,7 @@ ms.date: 08/04/2023
 ms.custom: known-issue
 ---
 
-# Known issue  - Workspace RP | Create workspace with bring your own storage scenario doesn't work in SDK V2 
+# Known issue  - Create workspace with bring your own storage scenario doesn't work in SDK V2 
 
 
 When following the document [Manage Azure Machine Learning workspaces in the portal or with the Python SDK (v2)](../how-to-manage-workspace.md) using a bring-your-own-storage scenario, the procedure fails if the storage is in a different subscription than the workspace.
