Fix grammar, broken links, and outdated content in SPFx docs (#10723)

* Fix grammar, broken links, and outdated content in SPFx docs

* Update links and improve wording in documentation

---------

Co-authored-by: Andrew Connell <me@andrewconnell.com>

Author: Ashlesha-MSFT

docs/spfx/dynamic-data.md

@@ -1,7 +1,7 @@
 ---
 title: Connect SharePoint Framework components using dynamic data
 description: High-level description on how to use dynamic data concept for connecting different SharePoint Framework components
-ms.date: 07/31/2020
+ms.date: 03/16/2026
 ms.localizationpriority: high
 ---
 
@@ -16,9 +16,9 @@ You can connect two or more SharePoint Framework components together and exchang
 
 ## Expose data using dynamic data source
 
-Dynamic data in the SharePoint Framework is based on the source-notification model. Components named as a dynamic data source, provide data and notify the SharePoint Framework when the data changes.
+Dynamic data in the SharePoint Framework is based on the source-notification model. Components acting as a dynamic data source provide data and notify the SharePoint Framework when the data changes.
 
-Other components on the page can subscribe to notifications issued by a dynamic data source. The SharePoint Framework notifies the consumer component that the source has notified its data has changed. The consumer component then requests the data from the source component.
+Other components on the page can subscribe to notifications issued by a dynamic data source. The SharePoint Framework notifies the consumer component that the source data has changed. The consumer component then requests the data from the source component.
 
 Every dynamic data source implements the `IDynamicDataCallables` interface.
 
@@ -34,7 +34,7 @@ export default class EventsWebPart extends BaseClientSideWebPart<IEventsWebPartP
   /**
    * Currently selected event
    */
-  private _selectedEvent: IEvent;
+  private _selectedEvent: IEvent | undefined;
 
   /**
    * Event handler for selecting an event in the list
@@ -71,7 +71,7 @@ export default class EventsWebPart extends BaseClientSideWebPart<IEventsWebPartP
    * Return the current value of the specified dynamic data set
    * @param propertyId ID of the dynamic data set to retrieve the value for
    */
-  public getPropertyValue(propertyId: string): IEvent | ILocation {
+  public getPropertyValue(propertyId: string): IEvent | ILocation | undefined {
     switch (propertyId) {
       case 'event':
         return this._selectedEvent;
@@ -155,7 +155,7 @@ The `getPropertyValue()` method returns the value for the particular type of dat
 
 To register a component as a dynamic data source, call the `this.context.dynamicDataSourceManager.initializeSource()` method and pass the instance of the dynamic data source as a parameter. In the previous example, the web part itself implements the `IDynamicDataCallables` interface, which is why the `initializeSource()` method is called with `this` as its argument.
 
-In the example code, the web part displays upcoming events in a list. Each time, the user selects an event from the list, the web part calls the `_eventSelected()` method. In that method, the web part assigns the selected event to the `_selectedEvent` class variable and issues a notification that the information about the selected event and location has changed by calling the `this.context.dynamicDataSourceManager.notifyPropertyChanged()` method passing the `id` of the definition that represents the changed data set.
+In the example code, the web part displays upcoming events in a list. Each time the user selects an event from the list, the web part calls the `_eventSelected()` method. In that method, the web part assigns the selected event to the `_selectedEvent` class variable and issues a notification that the information about the selected event and location has changed by calling the `this.context.dynamicDataSourceManager.notifyPropertyChanged()` method passing the `id` of the definition that represents the changed data set.
 
 ## Consume dynamic data in web parts
 
@@ -164,10 +164,14 @@ Web parts can consume data exposed by dynamic data sources present on the page.
 ```typescript
 import { DynamicProperty } from '@microsoft/sp-component-base';
 import {
-  DynamicDataSharedDepth,
-  IWebPartPropertiesMetadata,
+  type IPropertyPaneConfiguration,
+  PropertyPaneTextField,
   PropertyPaneDynamicFieldSet,
   PropertyPaneDynamicField
+} from '@microsoft/sp-property-pane';
+import {
+  BaseClientSideWebPart,
+  IWebPartPropertiesMetadata
 } from '@microsoft/sp-webpart-base';
 
 /**
@@ -347,7 +351,7 @@ export interface IMapWebPartProps {
 }
 ```
 
-In this example, the address is a string, but other types of data such as boolean, numbers or objects are supported as well. Web part properties defined as `DynamicProperty` can retrieve their data from dynamic data sources or values provided directly in the web part properties. Because the same web part property can be used for both dynamic data sources and static values configured in web part properties, you don't need to define multiple web part properties what simplifies building versatile web parts.
+In this example, the address is a string, but other types of data such as boolean, numbers or objects are supported as well. Web part properties defined as `DynamicProperty` can retrieve their data from dynamic data sources or values provided directly in the web part properties. Because the same web part property can be used for both dynamic data sources and static values configured in web part properties, you don't need to define multiple web part properties, which simplifies building versatile web parts.
 
 ### Define the type of data stored in dynamic properties
 

docs/spfx/enable-Microsoft-365-content-delivery-network.md

@@ -1,7 +1,7 @@
 ---
 title: Enable the Microsoft 365 CDN
 description: Enable the Microsoft 365 CDN on your Microsoft 365 Tenant
-ms.date: 02/08/2021
+ms.date: 03/16/2026
 ms.localizationpriority: medium
 ---
 # Enable the Microsoft 365 CDN
@@ -15,29 +15,29 @@ In this article, you'll learn how to enable the Microsoft 365 CDN on your ShareP
 
 ## Options for managing the Microsoft 365 CDN
 
-The Microsoft 365 CDN is managed using the command line and you can use PowerShell cmdlets or the cross-platform CLI for Microsoft 365 available through SharePoint PnP Community channels.
+The Microsoft 365 CDN is managed using the command line, and you can use PowerShell cmdlets or the cross-platform CLI for Microsoft 365 available through SharePoint PnP Community channels.
 
 ### Microsoft SharePoint Online Management Shell
 
-The Microsoft 365 CDN is managed by tenant administrators by using the **Microsoft SharePoint Online Management Shell**, a PowerShell module from Microsoft used to manage your SharePoint Online subscription in Office 365.
+The Microsoft 365 CDN is managed by tenant administrators by using the **Microsoft SharePoint Online Management Shell**, a PowerShell module from Microsoft used to manage your SharePoint Online subscription in Microsoft 365.
 
 Before using any of the cmdlets in the Microsoft SharePoint Online Management Shell module, you must first connect to SharePoint Online using the **Connect-SPOService** cmdlet. All CDN settings are managed using the ***-SPOTenantCdn** cmdlets.
 
-Learn more here: [Microsoft SharePoint Online Management Shell](https://technet.microsoft.com/library/fp161372.aspx)
+Learn more here: [Microsoft SharePoint Online Management Shell](/powershell/sharepoint/sharepoint-online/connect-sharepoint-online)
 
 ### CLI for Microsoft 365
 
 The CLI for Microsoft 365 is a cross-platform command-line interface that can be used on any platform, including Windows, macOS, and Linux. The CLI implements the same calls made by the SharePoint Online Management Shell without using PowerShell.
 
-Before using any of the commands in the CLI for Microsoft 365, you must first connect to Microsoft 365 tenant using the **m365 login** command.
+Before using any of the commands in the CLI for Microsoft 365, you must first connect to the Microsoft 365 tenant using the **m365 login** command.
 
 Learn more here: [CLI for Microsoft 365](https://pnp.github.io/cli-microsoft365?utm_source=msft_docs&utm_medium=page&utm_campaign=Use+SharePoint+Online+tenant+properties)
 
 [!INCLUDE [pnp-o365cli](../../includes/snippets/open-source/pnp-o365cli.md)]
 
 ## Get the Microsoft 365 CDN status
 
-Get the current status of public CDN settings from the tenant level by executing the following commands one-by-one:
+Get the current status of public CDN settings from the tenant level by executing the following commands one by one:
 
 # [Microsoft SPO Management Shell](#tab/msposh)
 
@@ -93,7 +93,7 @@ In this tutorial, we create a specific document library named **CDN** to act as
 
 ### Add a new CDN origin
 
-In this case, we're setting the origin as **\*/cdn**, which means that any relative folder with the name of **cdn** acts as a CDN origin.
+In this case, we're setting the origin as **\*/cdn**, which means that any relative folder named **cdn** acts as a CDN origin.
 
 # [Microsoft SPO Management Shell](#tab/msposh)