typo fixes from server.json to proper serve.json

Author: VesaJuvonen

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

@@ -162,7 +162,7 @@ You cannot use the local Workbench to test SharePoint Framework Extensions. You
     This dialog is thrown by your SharePoint Framework Extension. Note that because you provided the `testMessage` property as part of the debug query parameters, it's included in the alert message. You can configure your extension instances based on the client component properties, which are passed for the instance in runtime mode.
 
 > [!NOTE] 
-> If you have issues with debugging, double-check the pageUrl setting in the **server.json** file.
+> If you have issues with debugging, double-check the pageUrl setting in the **serve.json** file.
 
 ## Next steps
 

docs/spfx/extensions/get-started/building-simple-cmdset-with-dialog-api.md

@@ -145,7 +145,7 @@ You cannot currently use the local Workbench to test SharePoint Framework Extens
 
     Because our ListView Command Set is hosted from localhost and is running, we can use specific debug query parameters to execute the code in the list view.
 
-2. Open **serve.json** file from **config** folder. Update **pageUrl** attribute to match an URL of the list where you want to test the solution. After edits your server.json should look somewhat following.
+2. Open **serve.json** file from **config** folder. Update **pageUrl** attribute to match an URL of the list where you want to test the solution. After edits your serve.json should look somewhat following.
 
     ```json
     {
@@ -189,7 +189,7 @@ You cannot currently use the local Workbench to test SharePoint Framework Extens
 
     When the code compiles without errors, it serves the resulting manifest from https://localhost:4321.
 
-    This will also start your default browser within the URL defined in **server.json** file. Notice that at least in Windows, you can control which browser window is used by activating the preferred one before executing this command.
+    This will also start your default browser within the URL defined in **serve.json** file. Notice that at least in Windows, you can control which browser window is used by activating the preferred one before executing this command.
 
 4. Accept the loading of debug manifests by selecting **Load debug scripts** when prompted.
 

docs/spfx/extensions/get-started/building-simple-field-customizer.md

@@ -154,7 +154,7 @@ You cannot currently use the local Workbench to test SharePoint Framework Extens
 
     ![Creating items in the newly created list with different values in the Percent field](../../../images/ext-field-create-items-to-list.png)
 
-8. Move back to Visual Studio Code and open **serve.json** file from **config** folder. Update **InternalFieldName** attribute as **Percent** based on the field name, which we just created. Update also **pageUrl** attribute to match an URL of the list which we just created in preview steps. After edits your server.json should look somewhat following.
+8. Move back to Visual Studio Code and open **serve.json** file from **config** folder. Update **InternalFieldName** attribute as **Percent** based on the field name, which we just created. Update also **pageUrl** attribute to match an URL of the list which we just created in preview steps. After edits your serve.json should look somewhat following.
 
     ```json
     {
@@ -197,7 +197,7 @@ You cannot currently use the local Workbench to test SharePoint Framework Extens
 
     ![gulp serve](../../../images/ext-field-gulp-serve.png)
 
-    This will also start your default browser within the URL defined in **server.json** file. Notice that at least in Windows, you can control which browser window is used by activating the preferred one before executing this command.
+    This will also start your default browser within the URL defined in **serve.json** file. Notice that at least in Windows, you can control which browser window is used by activating the preferred one before executing this command.
 
 10. Accept the loading of debug manifests by selecting **Load debug scripts** when prompted.