Skip to content

Commit bb09cd5

Browse files
joelfmrodriguesVesaJuvonen
authored andcommitted
Update tenant-wide-deployment-extensions.md (SharePoint#3226)
1 parent 300de17 commit bb09cd5

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/spfx/extensions/basics/tenant-wide-deployment-extensions.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ App catalog site collection contains a **Tenant Wide Extensions** list, which ca
2727

2828
Specific SharePoint Framework extensions can be activated in the tenant level by adding entries to the **Tenant Wide Extension** list. Each entry can be targeted to specific web template or a list type, depending on the functional requirements.
2929

30-
These list specific configurations are resolved runtime when end users are accessing pages in content site collections. This means that the changes applied to this list are available for both existing and new sites in the tenant.
30+
These list specific configurations are resolved at runtime when end users are accessing pages in content site collections. This means that the changes applied to this list are available for both existing and new sites in the tenant.
3131

3232
SharePoint Framework solutions can contain automation which will add automatically entry to the Tenant Wide Extension list, when the solution is added
3333

@@ -139,4 +139,4 @@ When an administrator adds a solution which has a ClientSideInstance.xml file i
139139

140140
![SharePoint client-side solution scaffolded successfully](../../../images/ext-tenant-wide-solution-deployment.png)
141141

142-
After solution deployment, administrator can change the deployment settings from the **Tenant Wide Extension** list.
142+
After solution deployment, administrator can change the deployment settings from the **Tenant Wide Extension** list.

0 commit comments

Comments
 (0)