moving SDK include

Author: s-polly

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

@@ -15,7 +15,7 @@ ms.custom: known-issue
 
 [!INCLUDE [sdk v1](../includes/machine-learning-sdk-v1.md)]
 
-During machine learning deployments using an AKS cluster, you may receive an invalid certificate error, such as `{"code":"BadRequest","statusCode":400,"message":"The request is invalid.","details":[{"code":"KubernetesUnaccessible","message":"Kubernetes error: AuthenticationException. Reason: InvalidCertificate"}],`
+During machine learning deployments using an AKS cluster, you may receive an invalid certificate error, such as `{"code":"BadRequest","statusCode":400,"message":"The request is invalid.","details":[{"code":"KubernetesUnaccessible","message":"Kubernetes error: AuthenticationException. Reason: InvalidCertificate"}]`.
 
 
 **Status:** Open

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

@@ -13,7 +13,6 @@ ms.custom: known-issue
 
 # Known issue  - Existing Kubernetes compute can't be updated with `az ml compute attach` command
 
-
 [!INCLUDE [dev v2](../includes/machine-learning-dev-v2.md)]
 
 Updating a Kubernetes attached compute instance using the `az ml attach` command appears to succeed but doesn't.

articles/machine-learning/known-issues/jupyter-r-kernel-not-starting.md

@@ -15,14 +15,12 @@ ms.custom: known-issue
 
 [!INCLUDE [dev v2](../includes/machine-learning-dev-v2.md)]
 
-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()`
+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()`.
 
 **Status:** Open
 
-
 **Problem area:** Compute
 
-
 ## Symptoms
 
 After creating a new compute instance, try to launch R kernel in JupyterLab or a Jupyter notebook. The kernel fails to launch. You'll see the following messages in the Jupyter logs: