Clarify browser terminology in MSAL iOS guide

Author: genlin

support/entra/entra-id/app-integration/repeat-login-prompts-in-msal-ios-app.md

@@ -21,7 +21,7 @@ This issue is typically caused by web browser configurations that do not allow c
 
 The tutorial uses the MSAL to implement authentication. MSAL SDK facilitates authentication by automatically renewing tokens. It also enables single sign-on (SSO) between other apps on the device and manages user accounts.
 
-For SSO to function correctly, tokens must be shared between apps. To meet this requirement, you must use a token cache or a broker application, such as Microsoft Authenticator for iOS. Interactive authentication in MSAL requires a web browser. On iOS, MSAL uses the Safari system web browser by default for interactive authentication. This default setup supports SSO state sharing between apps.
+For SSO to function correctly, tokens must be shared between apps. To meet this requirement, you must use a token cache or a broker application, such as Microsoft Authenticator for iOS. Interactive authentication in MSAL requires a web browser. On iOS, MSAL uses the Safari system browser by default for interactive authentication. This default setup supports SSO state sharing between apps.
 
 However, if you customize the browser configuration for authentication, such as by using one of the following options, cookie sharing might not be enabled by default.
 
@@ -34,15 +34,14 @@ However, if you customize the browser configuration for authentication, such as
 
 To prevent repeated login prompts, you must allow cookie sharing when you customize the browser. To enable SSO and cookie sharing between MSAL and your iOS app, use one of the following solutions:
 
--	Use `ASWebAuthenticationSession` and Safari (`UIApplication.shared.open`)
+-	Use `ASWebAuthenticationSession` and Safari system browser (`UIApplication.shared.open`)
 
-   - Use Case: Your app uses MSAL together with the default `ASWebAuthenticationSession` instance, and you open external links or logout flows in  Safari.
-   
-   - **Note:** `ASWebAuthenticationSession` is the recommended method for MSAL interactive authentication on iOS 12+. It's the only supported method on iOS 13+. This method is privacy-preserving and shares cookies with Safari. SSO works between MSAL and Safari because they share cookies through the system authentication session.
+   - Use Case: Your app uses MSAL together with the default `ASWebAuthenticationSession` instance, and you open external links or logout flows in Safari system browser.
+   - **Note:** `ASWebAuthenticationSession` is the recommended method for MSAL interactive authentication on iOS 12+. It's the only supported method on iOS 13+. This method is privacy-preserving and shares cookies with system browser. SSO works between MSAL and Safari browser application because they share cookies through the system authentication session.
 -	Use `WKWebView`
    - Use Case: You explicitly configure MSAL to use `WKWebView`, and your app also uses `WKWebView` for related workflows.
 
-   - **Note:** You can use `WKWebView` for a consistent experience within your app. However, because it's sandboxed, `WKWebView` doesn't share session cookies with Safari or other apps. This condition limits support for SSO to within your app only.
+   - **Note:** You can use `WKWebView` for a consistent experience within your app. However, because it's sandboxed, `WKWebView` doesn't share session cookies with Safari system browser or other apps. This condition limits support for SSO to within your app only.
 
    For more information, see [Customizing webviews and browsers](/azure/active-directory/develop/customize-webviews).