Skip to content

Commit a0351ca

Browse files
grammatical fixes
1 parent c73a1eb commit a0351ca

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

docs/embedded/concepts/app-concepts/containertypes.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,8 @@ ms.localizationpriority: high
1010
A container type is a SharePoint Embedded resource that defines the relationship, access privileges, and billing accountability between a SharePoint Embedded application and a set of containers. Also, the container type defines behaviors on the set of containers.
1111

1212
Each container type is strongly coupled with one SharePoint Embedded application, which is referred to as the owning application. The owning application developer is responsible for creating and managing their container types.
13-
SharePoint Embedded mandates a 1:1 relationship between owning application and container type.
13+
14+
SharePoint Embedded mandates a 1:1 relationship between owning application and a container type.
1415

1516
Container type is represented on each container instance as an immutable property (ContainerTypeID) and is used across the entire SharePoint Embedded ecosystem, including:
1617

@@ -21,8 +22,8 @@ Container type is represented on each container instance as an immutable propert
2122

2223
> [!NOTE]
2324
>
24-
> 1. You must specify the purpose of the container type you're creating at creation time. Depending on the purpose, you may or may not need to provide your Azure Subscription ID. A container type set for trial purpose can't be converted for production; or vice versa.
25-
> 1. You must use the latest version of SharePoint PowerShell for container type configurations. For permissions and the most current information about Windows PowerShell for SharePoint Embedded, see the documentation at [Intro to SharePoint Embedded Management Shell](/powershell/sharepoint/sharepoint-online/introduction-sharepoint-online-management-shell).
25+
> 1. You must specify the purpose of the container type you're creating at creation time. Depending on the purpose, you may or may not need to provide your Azure Subscription ID. A container type set for trial purposes can't be converted for production; or vice versa.
26+
> 1. You must use the latest version of SharePoint PowerShell to configure a container type. For permissions and the most current information about Windows PowerShell for SharePoint Embedded, see the documentation at [Intro to SharePoint Embedded Management Shell](/powershell/sharepoint/sharepoint-online/introduction-sharepoint-online-management-shell).
2627
2728
## Trial use
2829

@@ -48,12 +49,12 @@ The following restrictions are applied to trial container types:
4849

4950
## Standard/Non-trial use
5051

51-
A standard container type is linked to a billing profile, which can be either regular billing or direct-to-consumer billing. Each developer tenant can create up to five standard container types.
52-
Standard container types are created using the [New-SPOContainerType](/powershell/module/sharepoint-online/new-spocontainertype) cmdlet. For container types with regular billing, create a billing profile using the [Add-SPOContainerTypeBilling](/powershell/module/sharepoint-online/add-spocontainertypebilling) cmdlet. For container types with direct to customer billing, use the flag `-IsPassThroughBilling`. For a direct to customer billed container type, there's no need to attach a billing profile.
52+
A standard container type is linked to a billing profile, which can be regular or direct-to-consumer billing. Each developer tenant can create up to five standard container types.
53+
Standard container types are created using the [New-SPOContainerType](/powershell/module/sharepoint-online/new-spocontainertype) cmdlet. For container types with regular billing, create a billing profile using the [Add-SPOContainerTypeBilling](/powershell/module/sharepoint-online/add-spocontainertypebilling) cmdlet. For container types with direct to customer billing, use the flag `-IsPassThroughBilling`. For the direct to customer billed container type, there's no need to attach a billing profile.
5354

5455
You need the following to create a standard container type:
5556

56-
- An Azure subscription and Resource Group must be present in the Azure portal for regular billing.
57+
- An Azure subscription and a resource group must be present in the Azure portal for regular billing.
5758
- An App registration must be created in Microsoft Entra ID
5859

5960
To create a standard container type with a regular billing profile, use the following cmdlets:
@@ -87,7 +88,7 @@ Set-SPOContainerTypeConfiguration -ContainerTypeId 4f0af585-8dcc-0000-223d-661eb
8788

8889
## Viewing Container Types
8990

90-
The Developer Admin can view all the SharePoint Embedded container types created by them on their tenant using `Get-SPOContainerType`. This cmdlet retrieves and returns the list of container types created for a SharePoint Embedded Application in the tenant.
91+
The Developer Admin can view all the SharePoint Embedded container types they created on their tenant using `Get-SPOContainerType`. This cmdlet retrieves and returns the list of container types created for a SharePoint Embedded Application in the tenant.
9192

9293
```powershell
9394
Get-SPOContainerType [<CommonParameters>]
@@ -115,6 +116,5 @@ Developer admins can delete both trial and standard container types. To delete a
115116
Once all the containers are deleted, Developer admins can delete the container type using `Remove-SPOContainerType`.
116117

117118
```powershell
118-
Remove-SPOContainerType
119-
[-ContainerTypeId <ContainerTypeId>]
119+
Remove-SPOContainerType [-ContainerTypeId <ContainerTypeId>]
120120
```

0 commit comments

Comments
 (0)