Merge pull request SharePoint#7915 from andrewconnell/content-fix/issue7904

andrewconnell · web-flow · commit 62709da508b2 · 2022-04-25T07:50:20.000-04:00
Fix typos &amp; broken links on multiple page
diff --git a/docs/design/semantic_slots.md b/docs/design/semantic_slots.md
@@ -1,7 +1,7 @@
 ---
 title:  Designing for section backgrounds using semantic slots
 description: Learn how to design your web part to take advantage of section backgrounds using semantic slots.
-ms.date: 04/06/2022
+ms.date: 04/25/2022
 ms.localizationpriority: medium
 ---
 
@@ -15,7 +15,7 @@ Section background is a feature that applies background color to a canvas secti
 
 ## Variant vs. Section background
 
-A variant describes different values of color generated from an existing theme. A variant will share the same set of colors as the original theme it was generated from, but will apply those colors differently. See [Office UI Fabric variant documentation](https://github.com/OfficeDev/office-ui-fabric-react/blob/master/packages/variants/README.md) for more detail.
+A variant describes different values of color generated from an existing theme. A variant will share the same set of colors as the original theme it was generated from, but will apply those colors differently. See [@fluentui/scheme-utilities](https://github.com/microsoft/fluentui/blob/master/packages/scheme-utilities/README.md) for more detail.
 
 A Section Background allows the user to apply a variant color from the theme to a canvas section. Both concepts share "Neutral", "Soft", and "Strong" options and can be used interchangeably when describing color usage.
 
@@ -25,39 +25,16 @@ A semantic slot is a theming slot that targets specific page elements. A Offic
 
 For example, default text uses the "bodyText" semantic slot. On the None, Neutral, and Soft section backgrounds, bodyText is assigned neutralPrimary. On the Strong section background, the palette color of bodyText changes to white. Semantic slots can be assigned palette colors for all variants in dark themes as well.
 
-In the table below, you can see all eight palette colors defined for the bodyText slot. 
+In the table below, you can see all eight palette colors defined for the bodyText slot.
 
 ![Example table showing semantic slots on light and dark theme variants](../images/doc-semantic-slot-940px-table.png)
 
-<br/> 
-<table>
-<tr>
-<td> </td>
-<td> Light themes</td>
-<td> Dark themes</td>
-</tr>
-<tr>
-<td>None</td>
-<td>neutralPrimary #333333</td>
-<td>neutralPrimary #ffffff</td>
-</tr>
-<tr>
-<td>Neutral</td>
-<td style="background-color:red">neutralPrimary #333333</td>
-<td>neutralPrimary #ffffff</td>
-</tr>
-<tr>
-<td>Soft</td>
-<td>neutralPrimary #333333</td>
-<td>neutralPrimary #ffffff</td>
-</tr>
-<tr>
-<td>Strong</td>
-<td>white #ffffff</td>
-<td>white #1f1f1f</td>
-</tr>
-</table>
-<br/>
+|         |      Light themes      |      Dark themes       |
+| ------- | ---------------------- | ---------------------- |
+| None    | neutralPrimary #333333 | neutralPrimary #ffffff |
+| Neutral | neutralPrimary #333333 | neutralPrimary #ffffff |
+| Soft    | neutralPrimary #333333 | neutralPrimary #ffffff |
+| Strong  | white #ffffff          | white #ffffff          |
 
 > [!NOTE]
 > The current semantic slot list is defined by commonly used design patterns in SharePoint. We want to avoid creating case-specific semantic slots. When designing a new web part, consider aligning to an existing design pattern. Office UI Fabric's policy is that semantic slots may never be removed from the list, so any additions are permanent.
diff --git a/docs/spfx/debug-in-vscode.md b/docs/spfx/debug-in-vscode.md
@@ -1,7 +1,7 @@
 ---
 title: Debug SharePoint Framework solutions in Visual Studio Code
 description: Prerequisites and steps for configuring Visual Studio Code for debugging SharePoint Framework solutions.
-ms.date: 02/10/2022
+ms.date: 04/25/2022
 ms.prod: sharepoint
 ms.localizationpriority: high
 ---
@@ -21,11 +21,6 @@ The default SharePoint Framework web parts and extensions project templates incl
 
 You also need **Google Chrome**. [Download and install the latest version of Google Chrome](https://www.google.com/chrome/browser/desktop/index.html).
 
-> [!TIP]
-> If you're using a version of SharePoint Framework Yeoman generator that is older than version 1.3.4, you can [install the Chrome debugger extension for Visual Studio Code from the Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome).
-
-In case you want to debug your projects with **Microsoft Edge**, you need to [install the Debugger for Edge extension for Visual Studio Code from the Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-edge) and follow the steps in [Debugging with Microsoft Edge or older projects](#debugging-with-microsoft-edge-or-older-projects).
-
 ## Debug configurations
 
 You can locate the debug configurations in the **./vscode/launch.json** file under the Visual Studio Code workspace folder. The **launch.json** contains two debug configurations:
diff --git a/docs/spfx/set-up-your-development-environment.md b/docs/spfx/set-up-your-development-environment.md
@@ -1,7 +1,7 @@
 ---
 title: Set up your SharePoint Framework development environment
 description: Use any text editor to build SharePoint Framework solutions. You can use macOS, Windows, or Linux.
-ms.date: 03/24/2022
+ms.date: 04/25/2022
 ms.prod: sharepoint
 ms.localizationpriority: high
 ms.custom: scenarios:getting-started
@@ -22,7 +22,7 @@ You can also follow these steps by watching this video on the SharePoint PnP You
 
 ## Install Node.js
 
-Install the latest version of **[Node.js](https://www.nodejs.org) LTS v14**.
+Install the most recent LTS version of **[Node.js](https://www.nodejs.org) v14**.
 
 This version is the currently recommended version of Node.js to use with the SharePoint Framework (*unless otherwise specified below*).
 
@@ -172,13 +172,13 @@ npm list --global --depth=0️
 
 If you're having trouble trusting your self-signed certificate when you run **gulp trust-dev-cert** & you've verified that the correct versions of all dependencies are installed, one solution we usually see resolve the issue is to uninstall all globally installed packages, uninstall Node.js, reboot & start again.
 
-In some cases, executing the command **gulp trust-dev-cert**, doesn't have the wanted effect of trusting the self-signed development certificate on your machine. In rare cases such as these, you may need to delete a hidden folder that's generated in your profile folder. 
-Locate & delete the folder **{{homedir}}/.gcb-serve-data** for SPFx version earlier than v1.12.1. For later versions delete folder **{{homedir}}/.rushstack** then try to trust the self-signed development certificate again. Otherwise running **gulp untrust-dev-cert** will have same effect to remove the certificate files from the profile folder. 
+In some cases, executing the command **gulp trust-dev-cert**, doesn't have the wanted effect of trusting the self-signed development certificate on your machine. In rare cases such as these, you may need to delete a hidden folder that's generated in your profile folder.
+Locate & delete the folder **{{homedir}}/.gcb-serve-data** for SPFx version earlier than v1.12.1. For later versions delete folder **{{homedir}}/.rushstack** then try to trust the self-signed development certificate again. Otherwise running **gulp untrust-dev-cert** will have same effect to remove the certificate files from the profile folder.
 In case the certificate is not added to the Trusted Root Certification Authority despite running **gulp trust-dev-cert** because of some policies blocking the action, the **rushstack-serve.pem** file from **{{homedir}}/.rushstack** folder can be imported manually into the Certificate Manager under Trusted Root Certification Authority with a local admin account.
 
 ### Unable to Install Packages with NPM - Corporate Proxies
 
-If your development environment is behind a corporate proxy, you need to configure NPM to use that proxy. Refer to the [npm-config](https://docs.npmjs.com/misc/config) documents on how to configure your development environment behind a corporate proxy... specifically the **proxy** & **http-proxy** settings. More information: [How to setup Node.js and Npm behind a corporate web proxy](https://jjasonclark.com/how-to-setup-node-behind-web-proxy/)
+If your development environment is behind a corporate proxy, you need to configure NPM to use that proxy. Refer to the [npm-config](https://docs.npmjs.com/misc/config) documents on how to configure your development environment behind a corporate proxy... specifically the **proxy** & **http-proxy** settings. More information: [Configure NPM for a coporate web proxy](https://www.voitanos.io/blog/node-npm-fix-proxy-config/)
 
 ## See also
 
diff --git a/docs/spfx/sharepoint-2016-support.md b/docs/spfx/sharepoint-2016-support.md
@@ -1,7 +1,7 @@
 ---
 title: SharePoint Framework development with SharePoint 2016 Feature Pack 2
 description: SharePoint Server 2016 Feature Pack 2 supports SharePoint Framework client-side web parts hosted in classic SharePoint pages.
-ms.date: 12/28/2021
+ms.date: 04/25/2022
 ms.localizationpriority: high
 ---
 # SharePoint Framework development with SharePoint Server 2016 Feature Pack 2
@@ -100,3 +100,4 @@ For more information, see [issue #1002](https://github.com/SharePoint/sp-dev-doc
 
 - [SharePoint Framework Overview](sharepoint-framework-overview.md)
 - [SharePoint Framework development tools and libraries compatibility](compatibility.md)
+- [Definitive guide for developers: SharePoint Framework for SharePoint Server 2016](https://www.voitanos.io/blog/definitive-guide-sharepoint-framework-sharepoint-server-2016/)
diff --git a/docs/spfx/sharepoint-2019-support.md b/docs/spfx/sharepoint-2019-support.md
@@ -1,7 +1,7 @@
 ---
 title: SharePoint Framework development with SharePoint Server 2019 & SharePoint Server SE
 description: SharePoint Server 2019 supports SharePoint Framework client-side web parts in classic and modern pages, and extensions in modern pages.
-ms.date: 12/28/2021
+ms.date: 04/25/2022
 ms.localizationpriority: high
 ---
 # SharePoint Framework development with SharePoint Server 2019 & SharePoint Server SE
@@ -79,3 +79,5 @@ For more information, see [issue #1002](https://github.com/SharePoint/sp-dev-doc
 
 - [SharePoint Framework Overview](sharepoint-framework-overview.md)
 - [SharePoint Server 2019 development platform](../general-development/sharepoint-2019-development-platform.md)
+- [Definitive guide for developers: SharePoint Framework for SharePoint Server 2019](https://www.voitanos.io/blog/definitive-guide-sharepoint-framework-sharepoint-server-2019/)
+- [Definitive guide for developers: SharePoint Framework for SharePoint Server SE](https://www.voitanos.io/blog/definitive-guide-sharepoint-framework-sharepoint-server-subscription-edition/)
diff --git a/docs/spfx/sharepoint-framework-why.md b/docs/spfx/sharepoint-framework-why.md
@@ -38,3 +38,7 @@ Historically, developers created web parts as full trust C# assemblies that were
 However, current development models usually involve JavaScript running in a browser making REST API calls to the SharePoint and Microsoft 365 back-end workloads. C# assemblies don’t work in this world. Developers needed a new development model.
 
 The SharePoint Framework is the next evolution in SharePoint development.
+
+## See Also
+
+- [Why did Microsoft create the SharePoint Framework (SPFx)?](https://www.voitanos.io/blog/spfx-5w1h-why-did-microsoft-create-sharepoint-framework/)
diff --git a/docs/transform/modernize-guidance.md b/docs/transform/modernize-guidance.md
@@ -1,7 +1,7 @@
 ---
 title: SharePoint modernization guidance
 description: Modernization offerings that IT Teams can use with their customers
-ms.date: 01/27/2021
+ms.date: 04/25/2022
 ms.prod: sharepoint
 ms.localizationpriority: high
 ---
@@ -29,7 +29,7 @@ Check the [Strategy page](modernize-guidance-strategy.md) to learn more.
 
 ## Step 3: Execution
 
-Next is using the scan results from step 1 to build your modernization plan: you'll learn how to use the scan output to identify the sites to modernize and how to structure them in waves. Next you'll review and tailor the modernization scrips, prepare and validate the input for these scripts and finally run the modernization scripts.
+Next is using the scan results from step 1 to build your modernization plan: you'll learn how to use the scan output to identify the sites to modernize and how to structure them in waves. Next you'll review and tailor the modernization scripts, prepare and validate the input for these scripts and finally run the modernization scripts.
 
 Check the [Execution page](modernize-guidance-execution.md) to learn more.
 
