Skip to content

Commit 90d8d8b

Browse files
author
Larry Franks
committed
grammar/style
1 parent 313dad0 commit 90d8d8b

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

articles/machine-learning/how-to-manage-rest.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ The response should provide an access token good for one hour:
7272
}
7373
```
7474

75-
Make note of the token, as you'll use it to authenticate all additional administrative requests. You'll do so by setting an Authorization header in all requests:
75+
Make note of the token, as you'll use it to authenticate all administrative requests. You'll do so by setting an Authorization header in all requests:
7676

7777
```bash
7878
curl -h "Authorization:Bearer <YOUR-ACCESS-TOKEN>" ...more args...
@@ -341,17 +341,17 @@ providers/Microsoft.Storage/storageAccounts/<YOUR-STORAGE-ACCOUNT-NAME>"
341341

342342
## Create a workspace using customer-managed encryption keys
343343

344-
By default, metadata for the workspace is stored in an Azure Cosmos DB instance that Microsoft maintains. This data is encrypted using Microsoft-managed keys. Instead of using the Microsoft-managed key, you can also provide your own key. Doing so creates an [additional set of resources](./concept-data-encryption.md#azure-cosmos-db) in your Azure subscription to store your data.
344+
By default, metadata for the workspace is stored in an Azure Cosmos DB instance that Microsoft maintains. This data is encrypted using Microsoft-managed keys. Instead of using the Microsoft-managed key, you can also provide your own key. Doing so creates an [another set of resources](./concept-data-encryption.md#azure-cosmos-db) in your Azure subscription to store your data.
345345

346-
To create a workspaces that uses your keys for encryption, you need to meet the following prerequisites:
346+
To create a workspace that uses your keys for encryption, you need to meet the following prerequisites:
347347

348348
* The Azure Machine Learning service principal must have contributor access to your Azure subscription.
349349
* You must have an existing Azure Key Vault that contains an encryption key.
350-
* The Azure Key Vault must exist in the same Azure region where you will create the Azure Machine Learning workspace.
351-
* The Azure Key Vault must have soft delete and purge protection enabled to protect against data loss in case of accidental deletion.
350+
* The Azure Key Vault must exist in the same Azure region where you'll create the Azure Machine Learning workspace.
351+
* The Azure Key Vault must have soft delete and purge protection enabled to protect against data loss if there was accidental deletion.
352352
* You must have an access policy in Azure Key Vault that grants get, wrap, and unwrap access to the Azure Cosmos DB application.
353353

354-
To create a workspaces that uses a user-assigned managed identity and customer-managed keys for encryption, use the below request body. When using an user-assigned managed identity for the workspace, also set the `userAssignedIdentity` property to the resource ID of the managed identity.
354+
To create a workspace that uses a user-assigned managed identity and customer-managed keys for encryption, use the below request body. When using a user-assigned managed identity for the workspace, also set the `userAssignedIdentity` property to the resource ID of the managed identity.
355355

356356
```bash
357357
curl -X PUT \

0 commit comments

Comments
 (0)