(DOCSP-23249): Product naming (mongodb#2121)

* Clean up product naming

* Fix titles

* Comment

Author: cbush

source/help.txt

@@ -15,7 +15,7 @@ Get Help
 Overview
 --------
 
-MongoDB provides various resources for getting help with App Services.
+MongoDB provides various resources for getting help with Atlas App Services.
 
 Professional Support
 --------------------

source/introduction.txt

@@ -89,13 +89,13 @@ easy to share data across users and platforms.
 Use Atlas App Services
 ----------------------
 
-The Realm SDKs integrate with Atlas App Services to easily and securely work
+The Realm SDKs integrate with App Services to easily and securely work
 with data from your app:
 
 - Query MongoDB Atlas directly from the Realm SDKs using built-in
   MongoDB interfaces. You can also configure the :ref:`Atlas Data API <data-api>`
   to query MongoDB using an HTTP client in your app.
-- :ref:`Atlas App Services Users and Authentication <users-and-authentication>`
+- :ref:`App Services Users and Authentication <users-and-authentication>`
   provide built-in user management. Integrate with a
   :ref:`JWT authentication service <custom-jwt-authentication>` or directly with
   :ref:`third-party authentication providers <auth-providers>`,
@@ -150,5 +150,5 @@ Summary
   Realm Database synchronizes data in a background thread,
   abstracting away network usage so you don't have to worry about
   latency or dropped connections.
-- The Realm SDKs integrate with Atlas App Services to easily and securely work
+- The Realm SDKs integrate with App Services to easily and securely work
   with your data in Atlas.

source/migrate.txt

@@ -15,7 +15,7 @@ Overview
 If you have an existing app built with the Stitch SDKs, you should migrate your 
 app to use the new Realm SDKs. While much of the logic and flow of information 
 hasn't changed, there are a few important changes in the way your app connects to 
-App Services.
+Atlas App Services.
 
 Updating Your Existing Application
 ----------------------------------

source/realm-legacy.txt

@@ -4,7 +4,7 @@
 Realm (Legacy)
 ==============
 
-App Services uses Realm Database version 10 and above. The
+Atlas App Services uses Realm Database version 10 and above. The
 documentation for earlier versions of Realm Database can be found
 on at `Realm documentation (legacy)
 <https://www.mongodb.com/docs/realm-legacy/docs/>`_.

source/sdk.txt

@@ -22,7 +22,7 @@ and platforms. Each SDK is language-idiomatic and includes:
 
 - The core database APIs for creating and working with on-device databases.
 
-- The APIs you need for connecting to the App Services backend so you can 
+- The APIs you need for connecting to the Atlas App Services backend so you can 
   make use of server-side features like :ref:`Sync <sync>`, 
   :ref:`Authentication <users-and-authentication>`, :ref:`Functions <functions>`, 
   :ref:`Triggers <trigger-types>`, and more. 

source/sdk/dotnet.txt

@@ -32,7 +32,7 @@ The Realm .NET SDK enables client applications written in C# for the .NET,
 `UWP <https://docs.microsoft.com/en-us/windows/uwp/get-started/>`__, `Xamarin
 <https://dotnet.microsoft.com/apps/xamarin>`__, and `Unity
 <https://unity.com/>`_ platforms to access data stored in local realms and
-interact with App Services services like Functions, MongoDB Data Access, and
+interact with Atlas App Services services like Functions, MongoDB Data Access, and
 authentication.
 
 .. _dotnet_supported-platforms:

source/sdk/dotnet/examples/flexible-sync.txt

@@ -64,7 +64,7 @@ You can:
 - Remove individual subscriptions or all subscriptions of a type
 
 When the data matches the subscription, and the authenticated user has the
-appropriate permissions, App Services syncs the backend data with the client app.
+appropriate permissions, Atlas App Services syncs the backend data with the client app.
 
 You can specify a string name for your subscription. If you do not give your
 subscription a name, the name is set to null.

source/sdk/dotnet/examples/open-a-realm.txt

@@ -54,7 +54,7 @@ Synced Realms
 To open a synced realm, you must have an authenticated 
 :dotnet-sdk:`User <reference/Realms.Sync.User.html>` object.  To 
 obtain an initial ``User`` instance, you need to authenticate against the 
-App Services backend, which requires the device to be online  
+Atlas App Services backend, which requires the device to be online  
 the first time a user logs in. Once initial authentication has occurred, you can 
 :ref:`retrieve an existing user <dotnet-retrieve-current-user>` while offline.
 

source/sdk/dotnet/examples/users/create-and-delete-users.txt

@@ -1,8 +1,8 @@
 .. _dotnet-create-and-delete-users:
 
-===================================
+==================================
 Create and Delete Users - .NET SDK
-===================================
+==================================
 
 .. default-domain:: mongodb
 
@@ -22,7 +22,7 @@ email/password authentication, Atlas App Services automatically creates a
 :ref:`user object <user-objects>` the first time a user authenticates. 
 When you use email/password authentication, you must first :ref:`register 
 <dotnet-email-password-register-new-user>` and :ref:`confirm 
-<dotnet-email-password-confirm-user>` a user before Atlas App Services 
+<dotnet-email-password-confirm-user>` a user before App Services 
 creates the user object.
 
 .. _dotnet-delete-user:

source/sdk/dotnet/examples/users/manage-user-api-keys.txt

@@ -14,7 +14,7 @@ Manage User API Keys - .NET SDK
    :class: singlecol
 
 Application users can generate user API keys with the .NET SDK. You
-can allow devices or services to communicate with App Services
+can allow devices or services to communicate with Atlas App Services
 on behalf of a user by associating a unique user API key with each
 device or service.
 

source/sdk/dotnet/examples/users/multi-user-applications.txt

@@ -44,7 +44,7 @@ The following states describe an on-device user at any given time:
 
   - **Active**: a single authenticated user that is currently using the
     app on a given device. The SDK associates this user with outgoing
-    requests and App Services evaluates data access permissions and runs
+    requests and Atlas App Services evaluates data access permissions and runs
     functions in this user's context. See :ref:`active user <active-user>` for
     more information.
 

source/sdk/dotnet/examples/users/user-metadata.txt

@@ -1,8 +1,8 @@
 .. _dotnet-user-metadata:
 
-=========================
+========================
 User Metadata - .NET SDK
-=========================
+========================
 
 .. default-domain:: mongodb
 
@@ -34,7 +34,7 @@ User metadata options vary depending on which provider you're using and
 
 .. warning:: User Metadata May Be Stale
 
-   App Services fetches the most recent version of user metadata when a user
+   Atlas App Services fetches the most recent version of user metadata when a user
    logs in. If the user changes their email address or profile photo with a 
    login provider, for example, those changes do not update in user metadata 
    until the user logs in again. Because we cache credentials and enable you 

source/sdk/dotnet/examples/work-with-users.txt

@@ -1,8 +1,8 @@
 .. _dotnet-work-with-users:
 
-===========================
+==========================
 Work with Users - .NET SDK
-===========================
+==========================
 
 .. default-domain:: mongodb
 
@@ -20,7 +20,7 @@ Work with Users - .NET SDK
 Overview
 --------
 
-When you use App Services to back your client app, you get access to a
+When you use Atlas App Services to back your client app, you get access to a
 :ref:`user object <user-objects>`. You can use the .NET SDK to:
 
 - Create and delete users
@@ -78,7 +78,7 @@ realm or call a function upon subsequent app opens.
 User Sessions
 ~~~~~~~~~~~~~
 
-Atlas App Services manages sessions with access tokens and refresh tokens.
+App Services manages sessions with access tokens and refresh tokens.
 Client SDKs supply the logic to manage tokens, and provide them with requests.
 
 .. seealso:: 

source/sdk/dotnet/fundamentals/application-services.txt

@@ -17,7 +17,7 @@ Application Services - .NET SDK
 Overview
 --------
 
-Realm provides SDKs that help you connect your client apps to the App Services
+Realm provides SDKs that help you connect your client apps to the Atlas App Services
 backend. The SDK provides the functionality needed to 
 authenticate users with any of the built-in :ref:`authentication providers <authentication-providers>`, 
 call backend :ref:`functions <functions>`, and directly access a linked

source/sdk/dotnet/fundamentals/write-transactions.txt

@@ -40,7 +40,7 @@ When you are done with your transaction, Realm either
 
 - When Realm **commits** a transaction, Realm writes
   all changes to disk. For synced realms, the SDK queues the change
-  for synchronization with App Services.
+  for synchronization with Atlas App Services.
 - When Realm **cancels** a write transaction or an operation in
   the transaction causes an error, all changes are discarded
   (or "rolled back").

source/sdk/dotnet/quick-start-with-sync.txt

@@ -47,7 +47,7 @@ statement:
 Initialize the App
 ------------------
 
-To use App Services features such as authentication and sync, you must
+To use Atlas App Services features such as authentication and sync, you must
 access your App using your App ID. You can find your App ID in the
 App Services UI. With that, you can initialize the realm app, as shown in the following 
 code:

source/sdk/dotnet/unity-tutorial.txt

@@ -282,7 +282,7 @@ Part 1: Set up the Game
          * - RealmScripts/AuthenticationManager.cs
            - Interacts with the TextField's of AuthenticationScreen.uxml to
              implement user login. In part 2, you'll add :ref:`user authentication
-             <dotnet-login-email-password>` with the App Services
+             <dotnet-login-email-password>` with the Atlas App Services
              :ref:`Email/Password <email-password-authentication>` provider.
 
          * - RealmScripts/RealmController.cs

source/sdk/flutter.txt

@@ -10,7 +10,7 @@ Flutter SDK (Beta)
    Install Realm for Flutter </sdk/flutter/install.txt>
    Quick Start </sdk/flutter/quick-start.txt>
    Realm Database </sdk/flutter/realm-database.txt>
-   App Services </sdk/flutter/app-services.txt>
+   Atlas App Services </sdk/flutter/app-services.txt>
    User Management </sdk/flutter/users.txt>
    Sync Device Data <sdk/flutter/sync.txt>
    API Reference <https://pub.dev/documentation/realm/latest/>
@@ -37,13 +37,13 @@ are specific configuration considerations:
 
 - The beta version of the SDK does not yet have certain Realm database features.
 - The SDK doesn't have built-in functionality to interact with all of
-  Atlas App Services. Learn more about how to :ref:`use the SDK with currently supported App Services
+  App Services. Learn more about how to :ref:`use the SDK with currently supported App Services
   <flutter-application-services>`.
 
 Get Started
 -----------
 
-To start using the Atlas App Services Flutter SDK
+To start using the Realm Flutter SDK
 in your Flutter application, see :ref:`Install Realm for Flutter
 <flutter-install>` to add the Flutter SDK
 dependency and then check out the :ref:`Quick Start

source/sdk/flutter/app-services.txt

@@ -28,7 +28,7 @@ backend using the Flutter SDK. Backend functionality includes:
 The Realm App Client
 --------------------
 
-To connect to your Atlas App Services backend, start with an
+To connect to your App Services backend, start with an
 :flutter-sdk:`App <realm/App-class.html>` object.
 This object provides all other functionality related to
 the backend. Initialize an App with the Realm app ID, which you can

source/sdk/flutter/app-services/connect-to-app.txt

@@ -17,7 +17,7 @@ backend. It provides access to the :ref:`authentication
 Before You Begin
 ----------------
 
-#. :ref:`Create an Atlas App Services app <create-a-realm-app>`
+#. :ref:`Create an App Services app <create-a-realm-app>`
 
 .. _flutter-access-the-app-client:
 
@@ -29,7 +29,7 @@ Access the App Client
    object with your App's App ID as the argument.
 #. Create an :flutter-sdk:`App <realm/App-class.html>`
    with the ``AppConfiguration`` you just created. You use this
-   ``App`` instance to access Atlas App Services features throughout your client application.
+   ``App`` instance to access App Services features throughout your client application.
 
 .. literalinclude:: /examples/generated/flutter/app_services_test.snippet.access-app-client.dart
    :language: dart
@@ -56,4 +56,4 @@ You can add optional arguments to the :flutter-sdk:`AppConfiguration <realm/AppC
 .. note::
 
    For most use cases, you only need your application's App ID to connect
-   to Atlas App Services. The other settings demonstrated here are optional.
+   to App Services. The other settings demonstrated here are optional.

source/sdk/flutter/realm-database.txt

@@ -76,7 +76,7 @@ a migration function.
 Sync
 ~~~~
 
-Device Sync adds network synchronization between a App Services backend and
+Device Sync adds network synchronization between a Atlas App Services backend and
 client devices on top of all of the functionality of Realm Database.
 When you use Realm Database with Sync, realms exist on device
 just like when you only use Realm Database. However, changes to

source/sdk/flutter/sync.txt

@@ -62,7 +62,7 @@ Enable Flexible Sync on the Backend
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 Before you can start syncing data from your client application using the SDK,
-you must enable Flexible Sync in the Atlas App Services backend.
+you must enable Flexible Sync in the App Services backend.
 
 To begin, refer to the :ref:`backend documentation on enabling Device Sync <enable-realm-sync>`.
 

source/sdk/flutter/users/authenticate.txt

@@ -21,7 +21,7 @@ used to instantiate ``Credentials`` objects for that authentication provider.
 Before You Begin
 ----------------
 
-#. :ref:`Create an Atlas App Services app <create-a-realm-app>`.
+#. :ref:`Create an App Services app <create-a-realm-app>`.
 #. Enable and configure one or more App Services :ref:`authentication providers <authentication-providers>`.
 
 .. _flutter-register:

source/sdk/flutter/users/custom-user-data.txt

@@ -25,7 +25,7 @@ in the backend. To learn more, see :ref:`Enable Custom User Data <custom-user-da
    from the SDK as well.
 
    You can create, update, or delete custom user data using one of the other
-   Realm SDKs, with App Services functions, or by directly querying Atlas.
+   Realm SDKs, with Atlas Functions, or by directly querying Atlas.
 
 Before You Begin
 ----------------

source/sdk/flutter/users/email-password-users.txt

@@ -10,14 +10,14 @@ Email/Password Users - Flutter SDK
    :depth: 2
    :class: singlecol
 
-With App Services's email/password authentication provider, you can register a new
+With Atlas App Services's email/password authentication provider, you can register a new
 account, confirm an email address, and reset a user's password from client code.
 
 Before You Begin
 ----------------
 
 
-#. :ref:`Create an Atlas App Services app <create-a-realm-app>`.
+#. :ref:`Create an App Services app <create-a-realm-app>`.
 #. Before you begin writing client code, you should understand the different email/password
    authentication flows that App Services provides, and configure the backend implementation
    for your application. App Services has a variety of ways to confirm email/password
@@ -74,7 +74,7 @@ function when the user registers.
 Send a Confirmation Email
 ~~~~~~~~~~~~~~~~~~~~~~~~~
 
-You only need to send a confirmation email if you :ref:`configure Atlas App Services to handle
+You only need to send a confirmation email if you :ref:`configure App Services to handle
 user confirmation with an email <auth-send-a-confirmation-email>`.
 
 To confirm a newly-created user, pass a confirmation ``token`` and

source/sdk/java/advanced-guides/custom-user-data.txt

@@ -54,7 +54,7 @@ method on the ``User`` object of a logged in user:
 
 .. warning:: Custom Data May Be Stale
 
-   App Services does not dynamically update the value of
+   Atlas App Services does not dynamically update the value of
    :java-sdk:`User.customData() <io/realm/mongodb/User.html#getCustomData-->`
    immediately when underlying data changes. Instead, App Services
    fetches the most recent version of custom user data whenever a user

source/sdk/java/advanced-guides/multi-user-applications.txt

@@ -43,7 +43,7 @@ The following states describe an on-device user at any given time:
 
   - **Active**: a single authenticated user that is currently using the
     app on a given device. The SDK associates this user with outgoing
-    requests and App Services evaluates data access permissions and runs
+    requests and Atlas App Services evaluates data access permissions and runs
     functions in this user's context. See :ref:`active user <active-user>` for
     more information.
 

source/sdk/java/data-types/realmany.txt

@@ -20,7 +20,7 @@ Realm object fields that can contain any of several
 underlying types. You can store multiple ``RealmAny`` instances in
 ``RealmList``, ``RealmDictionary``, or ``RealmSet`` fields. To change
 the value of a ``RealmAny`` field, assign a new ``RealmAny`` instance
-with a different underlying value. In App Services backend
+with a different underlying value. In Atlas App Services backend
 :ref:`object schemas <object-schema>`, the ``RealmAny``
 data type is called **mixed**. ``RealmAny`` fields are indexable, but
 cannot be used as primary keys.

source/sdk/java/examples/authenticate-users.txt

@@ -335,7 +335,7 @@ users in your Android application:
 #. Use the :java-sdk:`app.loginAsync()
    <io/realm/mongodb/App.html#loginAsync-io.realm.mongodb.Credentials-io.realm.mongodb.App.Callback->`
    or :java-sdk:`app.login() <io/realm/mongodb/App.html#login-io.realm.mongodb.Credentials->`
-   methods to authenticate with the App Services backend using the token.
+   methods to authenticate with the Atlas App Services backend using the token.
 
 The following code implements this flow, starting with a method call to
 ``loginWithGoogle()``:
@@ -396,7 +396,7 @@ to ``app.login()`` or ``app.loginAsync()``.
 Offline Login
 -------------
 
-Atlas App Services manages sessions with access tokens and refresh tokens. Client
+App Services manages sessions with access tokens and refresh tokens. Client
 SDKs supply the logic to manage tokens, and provide them with requests.
 
 The SDK stores these tokens in 

source/sdk/java/fundamentals/application-services.txt

@@ -16,7 +16,7 @@ Application Services - Java SDK
 Overview
 --------
 
-Realm provides SDKs that help you connect your client apps to the App Services
+Realm provides SDKs that help you connect your client apps to the Atlas App Services
 backend. The SDK provides the functionality needed to 
 authenticate users with any of the built-in :ref:`authentication providers <authentication-providers>`, 
 call backend :ref:`functions <functions>`, and directly access a linked
@@ -33,7 +33,7 @@ App Services. Initialize the ``App`` object with the App ID, which you can
 .. seealso::
 
    To learn how to initialize the App client, see
-   :ref:`Connect to an Atlas App Services backend <java-init-appclient>`.
+   :ref:`Connect to an App Services backend <java-init-appclient>`.
 
 Authentication & User Management
 --------------------------------