apply review feedback

Author: ranbel

src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/protocol-handler.mdx

@@ -12,7 +12,7 @@ Administrators can automate WARP registration on managed devices and minimize th
 
 During the default WARP enrollment process, end users typically need to complete several steps in order to login:
 
-1. Review and accept Cloudflare's privacy policy in the WARP client GUI.
+1. Review Terms and Conditions in the WARP client GUI and acknowledge your company's use of Cloudflare WARP.
 2. Select their identity provider from the Cloudflare Access login screen.
 3. Complete the authentication steps required by the identity provider.
 4. Interact with a browser popup requesting permission to launch the WARP client.
@@ -23,6 +23,8 @@ This guide covers how to eliminate steps 1, 2 and 4 from your WARP deployment.
 If you are looking to eliminate all user interaction, you can [enroll devices using service tokens](/cloudflare-one/connections/connect-devices/warp/deployment/device-enrollment/#check-for-service-token). Because users are not required to log in to an identity provider, identity-based policies and logging will not be available on these devices.
 :::
 
+On iOS and Android / ChromeOS, end users will still be asked questions required by their platform such as accepting notifications or installing the VPN Profile.
+
 ## Turn off onboarding screens
 
 To skip the Terms and Conditions screens that are usually presented to users, set the [`onboarding` parameter](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/) to `false` in your [MDM deployment file](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/). Here is an example `mdm.xml` file:
@@ -68,12 +70,12 @@ To add the registry key manually:
 
 	Be sure to replace `<your-team-name>` with your actual <GlossaryTooltip term="team name">Zero Trust team name</GlossaryTooltip>.
 
-Instead of using the Registry Editor, the registry key can also be created using a Group Policy Object (GPO), PowerShell script, or with an MDM tool such as [Intune](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/partners/intune/#update-mdm-parameters).
+Instead of using the Registry Editor, the registry key can also be created using a Group Policy Object (GPO), PowerShell script, or with an MDM such as [Intune](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/partners/intune/#update-mdm-parameters).
 
 </TabItem>
 <TabItem label="macOS">
 
-On macOS, you can configure `AutoLaunchProtocolsFromOrigins` by deploying a property list (plist) file for the browser. The exact instructions will vary depending on your [MDM tool](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/partners/). The general procedure is as follows:
+On macOS, you can configure `AutoLaunchProtocolsFromOrigins` by deploying a property list (plist) file for the browser. The exact instructions will vary depending on your [MDM](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/partners/). The general procedure is as follows:
 
 1. Create a new plist file with the following name (case sensitive):
 	- Google Chrome: `com.google.Chrome.plist`
@@ -97,7 +99,7 @@ On macOS, you can configure `AutoLaunchProtocolsFromOrigins` by deploying a prop
 
 	Be sure to replace `<your-team-name>` with your actual <GlossaryTooltip term="team name">Zero Trust team name</GlossaryTooltip>.
 
-3. Some MDM tools require converting the `.plist` to a `.mobileconfig` before pushing it to a device. You can use a [file converter](https://github.com/timsutton/mcxToProfile) or modify the following example `com.google.Chrome.mobileconfig`:
+3. Some MDMs require converting the `.plist` to a `.mobileconfig` before pushing it to a device. You can use a [file converter](https://github.com/timsutton/mcxToProfile) or modify the following example `com.google.Chrome.mobileconfig`:
 
 		```xml
 		<?xml version="1.0" encoding="UTF-8"?>
@@ -165,7 +167,7 @@ On macOS, you can configure `AutoLaunchProtocolsFromOrigins` by deploying a prop
 		</dict>
 		</plist>
 		```
-4. Upload the `.plist` or `.mobileconfig` file to your preferred MDM tool.
+4. Upload the `.plist` or `.mobileconfig` file to your preferred MDM.
 5. Deploy the configuration profile to your devices.
 
 For more information on configuring browser policies on macOS, refer to the [Google Chrome](https://support.google.com/chrome/a/answer/9020077?hl=en&ref_topic=7650028&sjid=15337530832025656704-NA) or [Microsoft Edge](https://learn.microsoft.com/en-us/deployedge/configure-microsoft-edge-on-mac) documentation.