Merge pull request #9786 from MicrosoftDocs/danbrown-privacy-family

Update "Family" SKU references to "Home" in Windows privacy articles

windows/privacy/windows-11-endpoints-non-enterprise-editions.md

@@ -32,7 +32,7 @@ The following methodology was used to derive the network endpoints:
 > [!NOTE]
 > Microsoft uses global load balancers that can appear in network trace-routes. For example, an endpoint for *.akadns.net might be used to load balance requests to an Azure datacenter, which can change over time.
 
-## Windows 11 Family
+## Windows 11 Home
 
 | **Area** | **Description** | **Protocol** | **Destination** |
 |-----------|--------------- |------------- |-----------------|

windows/privacy/windows-endpoints-1809-non-enterprise-editions.md

@@ -32,7 +32,7 @@ We used the following methodology to derive these network endpoints:
 > [!NOTE]
 > Microsoft uses global load balancers that can appear in network trace-routes. For example, an endpoint for *.akadns.net might be used to load balance requests to an Azure datacenter, which can change over time.
 
-## Windows 10 Family
+## Windows 10 Home
 
 | **Destination** | **Protocol** | **Description** |
 | --- | --- | --- |

windows/privacy/windows-endpoints-1903-non-enterprise-editions.md

@@ -36,7 +36,7 @@ The following methodology was used to derive the network endpoints:
 > [!NOTE]
 > Microsoft uses global load balancers that can appear in network trace-routes. For example, an endpoint for *.akadns.net might be used to load balance requests to an Azure datacenter, which can change over time.
 
-## Windows 10 Family
+## Windows 10 Home
 
 | Destination | Protocol | Description |
 | ----------- | -------- | ----------- |

windows/privacy/windows-endpoints-1909-non-enterprise-editions.md

@@ -34,7 +34,7 @@ The following methodology was used to derive the network endpoints:
 > [!NOTE]
 > Microsoft uses global load balancers that can appear in network trace-routes. For example, an endpoint for *.akadns.net might be used to load balance requests to an Azure datacenter, which can change over time.
 
-## Windows 10 Family
+## Windows 10 Home
 
 | **Destination** | **Protocol** | **Description** |
 | --- | --- | --- |

windows/privacy/windows-endpoints-2004-non-enterprise-editions.md

@@ -35,7 +35,7 @@ The following methodology was used to derive the network endpoints:
 > [!NOTE]
 > Microsoft uses global load balancers that can appear in network trace-routes. For example, an endpoint for *.akadns.net might be used to load balance requests to an Azure datacenter, which can change over time.
 
-## Windows 10 Family
+## Windows 10 Home
 
 | **Destination** | **Protocol** | **Description** |
 | --- | --- | --- |

windows/privacy/windows-endpoints-20H2-non-enterprise-editions.md

@@ -34,7 +34,7 @@ The following methodology was used to derive the network endpoints:
 > [!NOTE]
 > Microsoft uses global load balancers that can appear in network trace-routes. For example, an endpoint for *.akadns.net might be used to load balance requests to an Azure datacenter, which can change over time.
 
-## Windows 10 Family
+## Windows 10 Home
 
 | **Area** | **Description** | **Protocol** | **Destination** |
 |-----------|--------------- |------------- |-----------------|

windows/privacy/windows-endpoints-21H1-non-enterprise-editions.md

@@ -34,7 +34,7 @@ The following methodology was used to derive the network endpoints:
 > [!NOTE]
 > Microsoft uses global load balancers that can appear in network trace-routes. For example, an endpoint for *.akadns.net might be used to load balance requests to an Azure datacenter, which can change over time.
 
-## Windows 10 Family
+## Windows 10 Home
 
 | **Area** | **Description** | **Protocol** | **Destination** |
 |-----------|--------------- |------------- |-----------------|