Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed some grammar issues #3960

Merged
merged 4 commits into from
May 23, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion documentation/Add-PnPOrgAssetsLibrary.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ title: Add-PnPOrgAssetsLibrary

* SharePoint: Access to the SharePoint Tenant Administration site

Adds a given document library as a organizational asset source
Adds a given document library as an organizational asset source

## SYNTAX

Expand Down
2 changes: 1 addition & 1 deletion documentation/Add-PnPTenantSequence.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ Add-PnPTenantSequence -Template <ProvisioningHierarchy> -Sequence <ProvisioningS

## DESCRIPTION

Allows to add a a tenant sequence object to a tenant template.
Allows to add a tenant sequence object to a tenant template.

## EXAMPLES

Expand Down
4 changes: 2 additions & 2 deletions documentation/Add-PnPTenantSequenceSite.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ title: Add-PnPTenantSequenceSite
# Add-PnPTenantSequenceSite

## SYNOPSIS
Adds a existing tenant sequence site object to a tenant template
Adds an existing tenant sequence site object to a tenant template

## SYNTAX

Expand All @@ -21,7 +21,7 @@ Add-PnPTenantSequenceSite -Site <ProvisioningSitePipeBind> -Sequence <Provisioni

## DESCRIPTION

Allows to add a existing tenant sequence site object to a tenant template.
Allows to add an existing tenant sequence site object to a tenant template.

## EXAMPLES

Expand Down
2 changes: 1 addition & 1 deletion documentation/Add-PnPWebPartToWikiPage.md
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@ This will add the web part as defined by the XML in the $webpart variable to the
## PARAMETERS

### -AddSpace
Must there be a extra space between the web part
Must there be an extra space between the web part

```yaml
Type: SwitchParameter
Expand Down
2 changes: 1 addition & 1 deletion pages/articles/batching.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ If you add a list item with Add-PnPListItem without batching, the following happ

All in all you see we make around 6 requests, although the exact number depends a bit on what type of fields you are setting. So if you loop through 100 items, you get at least 600 requests.

## Adding a item with batching (REST)
## Adding an item with batching (REST)

```powershell
$batch = New-PnPBatch
Expand Down
2 changes: 1 addition & 1 deletion pages/articles/connecting.md
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ You will have to create your own Azure AD Application registration, or you can c
Register-PnPAzureADApp -ApplicationName "YourApplicationName" -Tenant [tenant].onmicrosoft.com -Interactive
```

This will launch a authentication dialog where you need to authenticate. After closing this window the cmdlet will continue to register a new application with a set of default permissions. By default a certificate will be generated and stored in the current folder, named after the application you want to create. You can specify your own certificate by using the `-CertificatePath` parameter and optional `-CertificatePassword` parameter.
This will launch an authentication dialog where you need to authenticate. After closing this window the cmdlet will continue to register a new application with a set of default permissions. By default a certificate will be generated and stored in the current folder, named after the application you want to create. You can specify your own certificate by using the `-CertificatePath` parameter and optional `-CertificatePassword` parameter.

You can add permissions by using the `-GraphApplicationPermissions`, `-GraphDelegatePermissions`, `-SharePointApplicationPermissions` or `-SharePointDelegatePermissions` parameters. The cmdlet will output the Azure AppId/client id, the name and location of the certificates created (if any) and the thumbprint of the certificate. It is possible to add the certificate created to the certificate management store in Windows by adding the `-Store` parameter.

Expand Down
Loading