Update per reviewer's comments

Author: v-lianna

support/windows-server/remote/set-up-remote-desktop-licensing-across-domains-forests-workgroups.md

@@ -1,16 +1,16 @@
 ---
 title: Set up RD licensing across domains forests or workgroups
 description: This article talks about the questions around the supportability (or recommended approach) of setting up Remote Desktop (RD) licensing across domain, forest, or work groups.
-ms.date: 01/15/2025
+ms.date: 03/31/2025
 manager: dcscontentpm
 audience: itpro
 ms.topic: troubleshooting
-ms.reviewer: kaushika, akhleshs, sabinn
+ms.reviewer: kaushika, akhleshs, sabinn, warrenw
 ms.custom:
 - sap:remote desktop services and terminal services\licensing for remote desktop services (terminal services)
 - pcy:WinComm User Experience
 ---
-# Best practices for setting up RDS licensing across Active Directory domains/forests or work groups
+# Best practices for setting up RD licensing across Active Directory domains/forests or work groups
 
 This article provides information on the questions around the supportability (or recommended approach) of setting up Remote Desktop (RD) licensing across domain, forest, or work groups.
 
@@ -39,14 +39,14 @@ For both Per Device and Per User CALs issuance to work, the RD Session Host and
 
 Here is more information on these scenarios:
 
-- RDS Host and RDS licensing servers are in the same work group
+- RD Session Host and RD licensing servers are in the same work group
 
-  Consider the following points while configuring RDS and RDS licensing servers in a work group environment:
+  Consider the following points while configuring RDS and RD licensing servers in a work group environment:
 
-  - We can use ONLY Per Device CALs in a work group environment. So, you should install only Per Device CALs on RDS licensing server.
+  - We can use ONLY Per Device CALs in a work group environment. So, you should install only Per Device CALs on RD licensing server.
   - Per User CAL tracking and reporting is not supported in work group mode.
-  - RDS Host and RDS licensing server roles can both be installed on the same server.
-  - If you install RDS licensing server on a different server in the work group, ensure that the RDS server is able to access RDS licensing server.
+  - RD Session Host and RD licensing server roles can both be installed on the same server.
+  - If you install RD licensing server on a different server in the work group, ensure that the RDS server is able to access RD licensing server.
 
   In Windows 2008 R2, automatic license server discovery is no longer supported for RD Session Host servers. You must specify the name of a license server for the RD Session Host server to use by using Remote Desktop Session Host Configuration snap-in. For more information, see [Specify a License Server for an RD Session Host Server to Use](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc770585(v=ws.11)).
 
@@ -55,14 +55,14 @@ Here is more information on these scenarios:
   In an Active Directory Domain scenario, we can have RD Session Host and RD licensing servers either on the same server or different servers. Consider the following points while configuring RDS environment in a domain scenario:
 
   - You can install both (Per Device and Per User) CALs on RD licensing server.
-    
+
   - The computer account for the license server must be a member of the Terminal Server License Servers group in AD DS. If the license server is installed on a domain controller, the Network Service account must also be a member of the Terminal Server License Servers group.
 
-  - To restrict the issuance of RDS CALs, you can add RD Session Host Servers into Terminal Server Computers group on RD licensing server and then enable the License server security group policy setting on the RD licensing server.
-    
+  - To restrict the issuance of RDS CALs, you can add RD Session Host servers into Terminal Server Computers group on RD licensing server and then enable the License server security group policy setting on the RD licensing server.
+
   - The License server security group policy setting is located in Computer Configuration\Policies\Administrative Templates\Windows Components\Remote \RD licensing and can be configured by using either the Local Group Policy Editor or the Group Console (GPMC).
 
-- RDS Host Servers are in one domain/forest and RDS licensing server is in another domain/forest
+- RD Session Host servers are in one domain/forest and RD licensing server is in another domain/forest
 
   In this kind of scenario, you should consider the following points:
 
@@ -72,11 +72,11 @@ Here is more information on these scenarios:
 
   - To issue RDS Per User CALs to users in other domains, there must be a two-way trust between the domains, and the license server must be a member of the Terminal Server License Servers group in those domains.
 
-  - To restrict the issuance of RDS CALs, you can add RDS Host Servers into Terminal Server Computers group on RDS licensing servers.
+  - To restrict the issuance of RDS CALs, you can add RD Session Host servers into Terminal Server Computers group on RD licensing servers.
 
-  - Configure RDS licensing server on all RDS Host Servers in each domain/forest. You can do it through RDS host configuration snap-in or through a group policy.
+  - Configure RD licensing server on all RD Session Host servers in each domain/forest. You can do it through RD Session Host configuration snap-in or through a group policy.
 
-  - Add administrators group of each domain/forest in the local administrators of RDS licensing server. This way, you'll not get a prompt to enter your credentials when you'll open RDS host configuration snap-ins in trusted domains/forests.
+  - Add administrators group of each domain/forest in the local administrators of RD licensing server. This way, you'll not get a prompt to enter your credentials when you'll open RD Session Host configuration snap-ins in trusted domains/forests.
 
 ## Data collection