Skip to content

Commit aded69b

Browse files
AriGunawanVesaJuvonen
authored andcommitted
Fix typo (SharePoint#2469)
1 parent fdd8d9c commit aded69b

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/spfx/extensions/get-started/build-a-hello-world-extension.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -113,9 +113,9 @@ If your Application Customizer uses the **ClientSideComponentProperties** JSON i
113113
114114
You cannot use the local Workbench to test SharePoint Framework Extensions. You need to test them against a live SharePoint Online site. You don't have to however deploy your customization to the app catalog to do this, which makes the debugging experience simple and efficient.
115115
116-
1. Open the **server.json** file in the **config** folder.
116+
1. Open the **serve.json** file in the **config** folder.
117117
118-
Notice that this file has been updated with the default settings matching your project. Yuo can notice that there's a specific GUID mentioned under the customActions element. This is automatically updated to match your component when project was scaffold. If you will add new components or change the properties for the component, you will need to update this file for testing.
118+
Notice that this file has been updated with the default settings matching your project. You can notice that there's a specific GUID mentioned under the customActions element. This is automatically updated to match your component when project was scaffold. If you will add new components or change the properties for the component, you will need to update this file for testing.
119119
120120
2. Update pageURL to match your own tenant, which you want to use for testing. You can use any URL with modern experience. *This could be for example a welcome page of a new group associated team site, which would mean somewhat following URL:
121121

0 commit comments

Comments
 (0)