Merge pull request #277372 from alexbuckgit/alexbuckgit/docutune-autopr-20240605-213341-3327273-ignore-build

[BULK] - DocuTune - Minor formatting fixes (part 3)

Author: prmerger-automator[bot]

articles/machine-learning/how-to-interactive-jobs.md

@@ -154,7 +154,7 @@ By specifying interactive applications at job creation, you can connect directly
    > [!NOTE]
    > If you use `sleep infinity`, you will need to manually [cancel the job](./how-to-interactive-jobs.md#end-job) to let go of the compute resource (and stop billing). 
 
-2. Run command `az ml job create --file <path to your job yaml file> --workspace-name <your workspace name> --resource-group <your resource group name> --subscription <sub-id> `to submit your training job. For more details on running a job via CLI, check out this [article](./how-to-train-model.md). 
+2. Run command `az ml job create --file <path to your job yaml file> --workspace-name <your workspace name> --resource-group <your resource group name> --subscription <sub-id>` to submit your training job. For more details on running a job via CLI, check out this [article](./how-to-train-model.md). 
 
 ---
 ### Connect to endpoints

articles/search/search-indexer-field-mappings.md

@@ -146,7 +146,7 @@ Performs *URL-safe* Base64 encoding of the input string. Assumes that the input
 
 Only URL-safe characters can appear in an Azure AI Search document key (so that you can address the document using the [Lookup API](/rest/api/searchservice/lookup-document)). If the source field for your key contains URL-unsafe characters, such as `-` and `\`, use the `base64Encode` function to convert it at indexing time. 
 
-The following example specifies the base64Encode function on `metadata_storage_name `to handle unsupported characters.
+The following example specifies the base64Encode function on `metadata_storage_name` to handle unsupported characters.
 
 ```http
 PUT /indexers?api-version=2020-06-30