Skip to content

Commit 1fa6d49

Browse files
authored
Minor grammar fixes
1 parent e5c2743 commit 1fa6d49

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

15/umbraco-cms/reference/content-delivery-api/protected-content-in-the-delivery-api/server-to-server-access.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -4,17 +4,17 @@ description: How to fetch protected content from the Delivery API with a server-
44

55
# Server-to-server access to protected content in the Delivery API
66

7-
If protected content is consumed from Delivery API in a server-to-server context, the [interactive authorization flow](README.md) won't work. Instead, we have to utilise the OpenId Connect Client Credentials flow, which is configured in the application settings.
7+
If protected content is consumed from the Delivery API in a server-to-server context, the [interactive authorization flow](README.md) won't work. Instead, we have to utilize the OpenId Connect Client Credentials flow, which is configured in the application settings.
88

99
## Configuration
1010

11-
In the Delivery API, Client Credentials work by mapping known Members to client IDs and secrets. These Members are known as API Members. When an API consumer uses the Client Credentials of an API Member, the consumer efficiently assumes the identity of this API Member.
11+
In the Delivery API, Client Credentials map known Members to client IDs and secrets. These Members are known as API Members. When an API consumer uses the Client Credentials of an API Member, the consumer efficiently assumes the identity of this API Member.
1212

1313
{% hint style="info" %}
14-
An API Member works exactly the same as a regular Member, with the added option of authorizing with Client Credentials.
14+
An API Member works the same as a regular Member, with the added option of authorizing with Client Credentials.
1515
{% endhint %}
1616

17-
In the following configuration example, the Member "member@local" are mapped to a set of Client Credentials:
17+
In the following configuration example, the Member "member@local" is mapped to a set of Client Credentials:
1818

1919
{% code title="appsettings.json" %}
2020

@@ -44,7 +44,7 @@ In the following configuration example, the Member "member@local" are mapped to
4444

4545
{% endcode %}
4646

47-
After restarting the site, the backoffice will now list "member@local" as an API Member:
47+
After restarting the site, the backoffice will list "member@local" as an API Member:
4848

4949
![An API Member in the backoffice](images/api-member.png)
5050

@@ -83,11 +83,11 @@ await consumer.ExecuteAsync();
8383

8484
public static class Constants
8585
{
86-
// the base URL of the Umbraco site - change this to fit your own setup
86+
// the base URL of the Umbraco site - change this to fit your custom setup
8787
public static string Host => "https://localhost:44391";
8888
}
8989

90-
// this is the API consumer, which will be listing the first few available content items - including protected ones.
90+
// This is the API consumer, which will be listing the first few available content items - including protected ones.
9191
public class ApiConsumerService
9292
{
9393
private readonly ApiAccessTokenService _apiAccessTokenService;
@@ -130,8 +130,8 @@ public class ApiConsumerService
130130
}
131131
}
132132

133-
// this service ensures reuse of access tokens for the duration of their lifetime.
134-
// it must be registered as a singleton service to work properly.
133+
// This service ensures the reuse of access tokens for the duration of their lifetime.
134+
// It must be registered as a singleton service to work properly.
135135
public class ApiAccessTokenService
136136
{
137137
private readonly Lock _lock = new();

0 commit comments

Comments
 (0)