DOCSP-45120-change-sync-to-migration (#180)

* DOCSP-45120-change-sync-to-migration

* DOCSP-45120 removing constants

* DOCSP-45120 tech edit

* DOCSP-45120 fixing build

Author: ltran-mdb2

snooty.toml

@@ -46,8 +46,6 @@ toc_landing_pages = [
 [constants]
 connector-version = "2.7.0"
 ddl = ":abbr:`DDL (Data Definition Language)`"
-job = "sync job" #this will be updated to migration job in the near future.
-job_plural = "sync jobs" #this will be updated to migration jobs in the near future.
 migrator-api = "REST API Documentation"
 migrator-api-endpoints = "Endpoints"
 

source/api-docs.txt

@@ -21,7 +21,7 @@ Relational Migrator REST API
 The Relational Migrator REST API provides you with programmatic access 
 to Relation Migrator with HTTPS endpoints. The REST API is a 
 Relational Migrator service between your application and your source and 
-destination databases that you can send requests to manage your sync jobs.
+destination databases that you can send requests to manage your migration jobs.
 
 You don't need to install any additional extensions or packages to use 
 the Relational Migrator REST API. The functionality is part of the 
@@ -59,7 +59,7 @@ Use the Relational Migrator REST API when:
   ``WHERE DATEDIFF(CURDATE(), last_modified) <= 1`` to batch migrate 
   data on a cadence from your relational database to MongoDB. 
 
-- You want to programmatically create Relational Migrator sync jobs 
+- You want to programmatically create Relational Migrator migration jobs 
   dynamically. For example, using connection strings from 
   multiple databases without manually configuring them in the GUI.
 

source/code-generation/query-converter/test-converted-queries/compare-converted-queries.txt

@@ -14,7 +14,7 @@ You can use the :guilabel:`Test Queries` pane to compare source
 and destination queries, views, and stored procedure results 
 in Relational Migrator. The :guilabel:`Test Queries` can 
 help you verify the accuracy of converted code and
-show the source and destination data after you run a sync job.
+show the source and destination data after you run a migration job.
 
 About this Task
 ---------------

source/connection-strings/connection-strings.txt

@@ -14,7 +14,7 @@ Relational Migrator uses connection strings to connect to both
 the relational and MongoDB databases. You can create connection strings:
 
 - Using the UI when you create a project.
-- Using the UI when you create a sync job.
+- Using the UI when you create a migration job.
 - By manually providing the Uniform Resource Identifier (URI).
 
 Get Started

source/connection-strings/mongodb-database-connection-strings.txt

@@ -137,4 +137,4 @@ Results
 -------
 
 The MongoDB connection URI is optionally specified as part of the process for
-creating a Relational Migrator project or when creating a sync job.
+creating a Relational Migrator project or when creating a migration job.

source/getting-started.txt

@@ -20,7 +20,7 @@ Get Started with Relational Migrator
 
 Relational Migrator is a tool to help you migrate your relational 
 data to MongoDB. This page guides you through installing the tool 
-and running your first sync job.
+and running your first migration job.
 
 To get familiar with Relational Migrator capabilities, 
 features, and use cases, review the following resources:
@@ -64,16 +64,16 @@ Steps
       the destination data model that best matches your 
       application needs.
 
-   .. step:: Create a sync job
+   .. step:: Create a migration job
 
-      :ref:`Sync jobs <rm-sync-jobs>` move the data from relational 
-      tables to MongoDB collections. Sync jobs have two types: 
+      :ref:`Migration jobs <rm-sync-jobs>` move the data from relational 
+      tables to MongoDB collections. Migration jobs have two types: 
 
       - **Snapshot** for point in time migrations. 
       - **Continuous** for ongoing change data capture zero-downtime migrations.
 
       To start your migration to MongoDB, 
-      :ref:`create a sync job <rm-create-jobs>`.
+      :ref:`create a migration job <rm-create-jobs>`.
 
 .. toctree::
    :titlesonly:

source/getting-started/atlas-log-in.txt

@@ -13,7 +13,7 @@ Log In with Atlas
 You can optionally sign in to your Atlas account inside Relational 
 Migrator. If you log in, you can access the 
 :ref:`Query Converter <rm-query-converter>` feature and you can choose 
-destination clusters from a list when creating sync jobs.
+destination clusters from a list when creating migration jobs.
 
 Before you Begin
 ----------------

source/getting-started/migration-scenarios.txt

@@ -49,7 +49,7 @@ destination databases remain in sync.
 After the continuous sync migration completes, you can transfer users to
 the new application and shut down the legacy application.
 
-To learn more about sync jobs, see :ref:`rm-sync-jobs`.
+To learn more about migration jobs, see :ref:`rm-sync-jobs`.
 
 Currently Unsupported Migration Scenarios
 -----------------------------------------

source/includes/fact-calculated-fields-type.rst

@@ -1,3 +1,3 @@
 When defining :ref:`rm-calculated-fields` and :ref:`rm-id-field-customizations`, 
 Relational Migrator shows an initial data type of :guilabel:`default`. 
-When you run a sync job, Relational Migrator updates this data type.
+When you run a migration job, Relational Migrator updates this data type.

source/includes/fact-cdc-recoverable.rst

@@ -1,2 +1,2 @@
-You can recover a continuous sync job within 24 hours of failure. 
+You can recover a continuous migration job within 24 hours of failure. 
 For details, see :ref:`rm-sync-jobs-recoverability`.