Skip to content

Commit 680b2de

Browse files
authored
Update configuring-the-pnp-provisioning-engine.md
Fixed typo.
1 parent 44eba35 commit 680b2de

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/solution-guidance/configuring-the-pnp-provisioning-engine.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ Sometimes you do not want to extract all artifacts from a site, or only even a s
1212
## Extraction Configuration
1313

1414
There is a JSON schema available at https://aka.ms/sppnp-extract-configuration-schema. We will automatically update the schema referred to by that URL to a later version if new functionality comes available.
15-
If you create a JSON file use a modern editor, like Visual Studio Code, and you reference this schema will there willl be intellisense and descriptions of all the properties you can set.
15+
If you create a JSON file use a modern editor, like Visual Studio Code, and you reference this schema, there will be intellisense and descriptions of all the properties you can set.
1616

1717
Let's have a look at the following sample configuration
1818

@@ -67,4 +67,4 @@ By default the engine only exports the home page if you specify the ```Pages```
6767

6868
- [SharePoint Patterns and Practices](https://github.com/SharePoint/PnP/)
6969
- [SharePoint Developer Group at Microsoft Tech Community](https://techcommunity.microsoft.com/t5/SharePoint-Developer/bd-p/SharePointDev)
70-
- [PnP remote provisioning](pnp-remote-provisioning.md)
70+
- [PnP remote provisioning](pnp-remote-provisioning.md)

0 commit comments

Comments
 (0)