Skip to content

Commit a1b7cc1

Browse files
authored
Update opt-out-api-quickstart.md
1 parent 9f53446 commit a1b7cc1

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/communication-services/quickstarts/sms/opt-out-api-quickstart.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -19,10 +19,10 @@ This article describes how to enable opt-out management for your Azure Communica
1919

2020
- An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
2121
- An active Communication Services resource and connection string. See [Create a Communication Services resource](../create-communication-resource.md).
22-
- To enable Opt-out management on your Azure Communication Services resource, contact [[email protected]](mailto:[email protected]) to allow-list your `Immutable resource Id` (as listed on the **Properties** page in the Azure portal), and associated SMS-enabled toll-free numbers.
22+
- To enable Opt-out management on your Azure Communication Services resource, contact [[email protected]](mailto:[email protected]) to allowlist your `Immutable resource Id` (as listed on the **Properties** page in the Azure portal), and associated SMS-enabled toll-free numbers.
2323

2424
## Quickstart: Send OptOut API requests with API (HMAC)
25-
Sending is similar to SMS as described in the [Azure Communication Services Postman Tutorial](https://learn.microsoft.com/azure/communication-services/tutorials/postman-tutorial) with the difference of endpoints for OptOut Actions (Add, Remove, or Check) and body. The request body has the same structure for all actions, while the response content slightly differs.
25+
Sending an Opt-out API request is similar to SMS as described in the [Azure Communication Services Postman Tutorial](https://learn.microsoft.com/azure/communication-services/tutorials/postman-tutorial) with the difference of endpoints for OptOut Actions (Add, Remove, or Check) and body. The request body has the same structure for all actions, while the response content slightly differs.
2626

2727
### Endpoints
2828

@@ -62,7 +62,7 @@ Here are some examples in different languages.
6262
```
6363

6464
### Sample Response
65-
In general, response content are the same for all actions and contain the success or failure `HttpStatusCode` per recipient. The only difference is that the `Check` action, which also returns the `isOptedOut` flag.
65+
In general, response contents are the same for all actions and contain the success or failure `HttpStatusCode` per recipient. The only difference is that the `Check` action, which also returns the `isOptedOut` flag.
6666

6767
#### Response Status
6868
- 200 Ok

0 commit comments

Comments
 (0)