Changed to sdk v1

Author: s-polly

articles/machine-learning/known-issues/inferencing-invalid-certificate.md

@@ -17,7 +17,7 @@ During machine learning deployments using an AKS cluster, you may receive an inv
 
 
 
-[!INCLUDE [dev v2](../includes/machine-learning-dev-v2.md)]
+[!INCLUDE [sdk v1](../includes/machine-learning-sdk-v1.md)]
 
 **Status:** Open
 

articles/machine-learning/known-issues/inferencing-updating-kubernetes-compute-appears-to-succeed.md

@@ -24,11 +24,11 @@ Updating a Kubernetes attached compute instance using the `az ml attach` command
 
 ## Symptoms
 
-When running the command `az ml compute attach --resource-group <rgname> --workspace-name <ws name> --type Kubernetes --name <existing attached compute name(aaaaa)> --resource-id "<resource URI>" --namespace <deployment name>`, the Workspace UI displays a success message indicating that the compute update was successful, however the compute won't have changed.
+When running the command `az ml compute attach --resource-group <resource-group-name> --workspace-name <workspace-name> --type Kubernetes --name <existing-attached-compute-name> --resource-id "<cluster-resource-id>" --namespace <kubernetes-namespace>`, The CLI returns a success message indicating that the compute has been successfully updated. However the compute won't be updated.
 
 ## Cause
 
-The `az ml compute attach` command isn't currently supported for use with Kubernetes compute. At this time, the CLI v2 and SDK v2 don't allow updating any configuration of an existing Kubernetes compute.
+The "az ml compute attach" command currently does not support update existing Kubernetes compute. 
 
 
 ## Next steps