Skip to content

Commit b9b86f3

Browse files
authored
Fixed typos
1 parent 1ff3d96 commit b9b86f3

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

docs/spfx/sharepoint-2019-support.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ SharePoint 2019 supports SharePoint Framework client-side web parts in classic a
1313

1414
Because SharePoint Online and SharePoint 2019 have different release cycles for new capabilities, they also have different capabilities when it comes to the SharePoint Framework. SharePoint Online always uses the latest version of the SharePoint Framework, but SharePoint 2019 only supports the version that matches the server-side dependencies of the deployed packages.
1515

16-
SharePoint 2019 supports SharePoint Framework client-side web parts hosted on classic or modern SharePoint pages built by using the SharePoint Framework v1.4.1. SharePoint 2019 also supposed SharePoint Framework extensions hosted on modern SharePoint pages built using SharePoint Framework v1.4.1 This means that when you are targeting the SharePoint 2019 platform, you need to use the SharePoint Framework v1.4.1 due to the server-side version dependencies.
16+
SharePoint 2019 supports SharePoint Framework client-side web parts hosted on classic or modern SharePoint pages built by using the SharePoint Framework v1.4.1. SharePoint 2019 also supports SharePoint Framework extensions hosted on modern SharePoint pages built using SharePoint Framework v1.4.1. This means that when you are targeting the SharePoint 2019 platform, you need to use the SharePoint Framework v1.4.1 due to the server-side version dependencies.
1717

1818
Starting from v1.3, the SharePoint Framework Yeoman generator supports scaffolding solutions that use both the latest version of the SharePoint Framework meant for use with SharePoint Online, and solutions that can be used with SharePoint on-premises based on the v1.1.0 or v1.4.1 of the SharePoint Framework. You don't need to install a separate version of the SharePoint Framework Yeoman generator to scaffold solutions meant for use with SharePoint on-premises.
1919

@@ -29,10 +29,10 @@ The [Team-based development on the SharePoint Framework](team-based-development-
2929

3030
If you have existing SharePoint Framework solutions and you'd like to confirm which version of the SharePoint Framework was used for them, you'll need to check the following locations:
3131

32-
- **.yo-rc.json**. File in the solution's root folder that stores the SharePoint Framework Yeoman template version used when the solution was created.
33-
- **package.json**. File in the solution's root folder that contains references to package versions used in the solution.
34-
- **npm-shrinkwrap.json**. File in the solution's root folder that contains information about the exact versions used (if you used the `npm shrinkwrap` command to lock down the exact versions of the solution).
35-
- **package.json**. File in the *node_modules/@microsoft/sp-webpart-base* folder that contains a *version* attribute matching the used SharePoint Framework version, if you have installed packages to your solution.
32+
- **.yo-rc.json** file in the solution's root folder that stores the SharePoint Framework Yeoman template version used when the solution was created.
33+
- **package.json** file in the solution's root folder that contains references to package versions used in the solution.
34+
- **npm-shrinkwrap.json** file in the solution's root folder that contains information about the exact versions used (if you have used the `npm shrinkwrap` command to lock down the exact versions of the solution).
35+
- **package.json** file in the *node_modules/@microsoft/sp-webpart-base* folder that contains a *version* attribute matching the used SharePoint Framework version, if you have installed packages to your solution.
3636

3737
## See also
3838

0 commit comments

Comments
 (0)