diff --git a/HISTORY.rst b/HISTORY.rst
index 0b923f21a..6e3f139fb 100644
--- a/HISTORY.rst
+++ b/HISTORY.rst
@@ -1,6 +1,6 @@
-*****************************
-ShotGrid Python API Changelog
-*****************************
+*********************************************
+Flow Production Tracking Python API Changelog
+*********************************************
 
 Here you can see the full list of changes between each Python API release.
 
@@ -173,7 +173,7 @@ v3.0.32 (2016 Sep 22)
 
 - Optimized import speed of the API on Python 2.7.
 - Integrated the latest fixes to the ``mimetypes`` module.
-- Added ``nav_expand()`` method as an experimental, internal method for querying SG hierarchy. 
+- Added ``nav_expand()`` method as an experimental, internal method for querying SG hierarchy.
 - Ported all documentation to sphinx. See http://developer.shotgridsoftware.com/python-api.
 - Moved Changelog to dedicated HISTORY file.
 
diff --git a/README.md b/README.md
index 161612f5b..eaf1e9ccc 100644
--- a/README.md
+++ b/README.md
@@ -4,9 +4,9 @@
 [![Build Status](https://dev.azure.com/shotgun-ecosystem/Python%20API/_apis/build/status/shotgunsoftware.python-api?branchName=master)](https://dev.azure.com/shotgun-ecosystem/Python%20API/_build/latest?definitionId=108&branchName=master)
 [![Coverage Status](https://coveralls.io/repos/github/shotgunsoftware/python-api/badge.svg?branch=master)](https://coveralls.io/github/shotgunsoftware/python-api?branch=master)
 
-# ShotGrid Python API
+# Flow Production Tracking Python API
 
-ShotGrid provides a simple Python-based API for accessing ShotGrid and integrating with other tools. This is the official API that is maintained by ShotGrid Software (https://knowledge.autodesk.com/contact-support)
+Autodesk provides a simple Python-based API for accessing Flow Production Tracking and integrating with other tools. This is the official API that is maintained by Autodesk (https://knowledge.autodesk.com/contact-support)
 
 The latest version can always be found at http://github.com/shotgunsoftware/python-api
 
@@ -48,8 +48,8 @@ Integration and unit tests are provided.
 - A `tests/config` file (you can copy an example from `tests/example_config`).
 - Tests can be run individually like this: `nosetests --config="nose.cfg" tests/test_client.py`
     - Make sure to not forget the `--config="nose.cfg"` option. This option tells nose to use our config file.  This will exclude python 2- and 3-specific files in the `/lib` directory, preventing a failure from being reported by nose for compilation due to incompatible syntax in those files.
-- `test_client` and `tests_unit` use mock server interaction and do not require a ShotGrid instance to be available (no modifications to `tests/config` are necessary).
-- `test_api` and `test_api_long` *do* require a ShotGrid instance, with a script key available for the tests. The server and script user values must be supplied in the `tests/config` file. The tests will add test data to your server based on information in your config. This data will be manipulated by the tests, and should not be used for other purposes.
+- `test_client` and `tests_unit` use mock server interaction and do not require a Flow Production Tracking instance to be available (no modifications to `tests/config` are necessary).
+- `test_api` and `test_api_long` *do* require a Flow Production Tracking instance, with a script key available for the tests. The server and script user values must be supplied in the `tests/config` file. The tests will add test data to your server based on information in your config. This data will be manipulated by the tests, and should not be used for other purposes.
 - To run all of the tests, use the shell script `run-tests`.
 
 ## Release process
diff --git a/SECURITY.md b/SECURITY.md
index b8899696a..c32c73245 100644
--- a/SECURITY.md
+++ b/SECURITY.md
@@ -4,18 +4,18 @@
 
 At Autodesk, we know that the security of your data is critical to your studio’s
 operation.
-As the industry shifts to the cloud, ShotGrid knows that security and service
+As the industry shifts to the cloud, Flow Production Tracking knows that security and service
 models are more important than ever.
 
 The confidentiality, integrity, and availability of your content is at the top
 of our priority list.
-Not only do we have a team of ShotGrid engineers dedicated to platform security
+Not only do we have a team of Flow Production Tracking engineers dedicated to platform security
 and performance, we are also backed by Autodesk’s security team, also invests
 heavily in the security for broad range of industries and customers.
 We constantly reassess, develop, and improve our risk management program because
 we know that the landscape of security is ever-changing.
 
-If you believe you have found a security vulnerability in any ShotGrid-owned
+If you believe you have found a security vulnerability in any Flow Production Tracking-owned
 repository, please report it to us as described below.
 
 
@@ -32,4 +32,4 @@ configurations, reproduction steps, exploit code, impact, etc.
 
 ## Additional Information
 
-Please check out the [ShotGrid Security White Paper](https://help.autodesk.com/view/SGSUB/ENU/?guid=SG_Administrator_ar_general_security_ar_security_white_paper_html).
\ No newline at end of file
+Please check out the [Flow Production Tracking Security White Paper](https://help.autodesk.com/view/SGSUB/ENU/?guid=SG_Administrator_ar_general_security_ar_security_white_paper_html).
\ No newline at end of file
diff --git a/azure-pipelines-templates/run-tests.yml b/azure-pipelines-templates/run-tests.yml
index b73ca1eb0..34345a332 100644
--- a/azure-pipelines-templates/run-tests.yml
+++ b/azure-pipelines-templates/run-tests.yml
@@ -99,7 +99,7 @@ jobs:
       pytest -v --cov shotgun_api3 --cov-report xml --test-run-title="${{parameters.name}}-$(python.version)"
     displayName: Running tests
     env:
-      # Pass the values needed to authenticate with the Shotgun site and create some entities.
+      # Pass the values needed to authenticate with the Flow Production Tracking site and create some entities.
       # Remember, on a pull request from a client or on forked repos, those variables
       # will be empty!
       SG_SERVER_URL: $(ci_site)
diff --git a/docs/advanced/packaging.rst b/docs/advanced/packaging.rst
index 630a32f44..d46426e73 100644
--- a/docs/advanced/packaging.rst
+++ b/docs/advanced/packaging.rst
@@ -14,8 +14,8 @@ There are caveats you need to be aware of when creating such an app.
 ********************************
 HTTPS Validation and cacerts.txt
 ********************************
-When creating the connection to ShotGrid a file is used to validate the ShotGrid certificate. This
-file is located at ``shotgun_api3/lib/httplib2/cacerts.txt``. Because this file is not a Python
+When creating the connection to Flow Production Tracking, a file is used to validate the Flow Production Tracking
+certificate. This file is located at ``shotgun_api3/lib/httplib2/cacerts.txt``. Because this file is not a Python
 file imported by your application, py2app will not know to include it in your package, it will
 need to be explicitly specified in your ``setup.py`` file (edit the path based on the location
 where your ``shotgun_api3`` package is located)::
@@ -31,7 +31,7 @@ following structure::
     ./Contents/Resources/my_script.py
 
 Where in ``my_script.py`` you can access the ``cacerts.txt`` file using a relative path to pass it
-into the ShotGrid connection's constructor::
+into the Flow Production Tracking connection's constructor::
 
     ca_certs = os.path.join(os.path.dirname(__file__), 'shotgun_api3', 'cacerts.txt')
     sg = shotgun_api3.Shotgun('https://my-site.shotgrid.autodesk.com', 'script_name', 'script_key',
diff --git a/docs/authentication.rst b/docs/authentication.rst
index 445820248..0e5fe8572 100644
--- a/docs/authentication.rst
+++ b/docs/authentication.rst
@@ -2,7 +2,7 @@
 Authentication
 ##############
 
-In order to communicate with your ShotGrid server via the API, you must provide valid authentication credentials. The API allows you to authenticate with user-based, or script-based credentials.
+In order to communicate with your server via the API, you must provide valid authentication credentials. The API allows you to authenticate with user-based, or script-based credentials.
 
 *************************
 User-based Authentication
@@ -17,24 +17,24 @@ When authenticating as a user, you provide your normal login and password when i
 ***************************
 Script-based Authentication
 ***************************
-In order to authenticate as a script, your script must be :ref:`registered with ShotGrid and have a valid API key <setting_up_shotgrid>`. When creating your :class:`shotgun_api3.Shotgun` object, provide the ``script_name`` and ``api_key``.::
+In order to authenticate as a script, your script must be :ref:`registered with Flow Production Tracking and have a valid API key <setting_up_shotgrid>`. When creating your :class:`shotgun_api3.Shotgun` object, provide the ``script_name`` and ``api_key``.::
 
     sg = shotgun_api3.Shotgun("https://my-site.shotgrid.autodesk.com",
                               script_name="compress",
                               api_key="0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef")
 
-.. note:: When using script-based authentication, we **strongly** recommend you register each script separately with ShotGrid and have individual API keys for each. This allows you to track down each of your scripts and the actions they are performing much more accurately in the event logs.
+.. note:: When using script-based authentication, we **strongly** recommend you register each script separately with Flow Production Tracking and have individual API keys for each. This allows you to track down each of your scripts and the actions they are performing much more accurately in the event logs.
 
 
 .. _setting_up_shotgrid:
 
 Adding Script Users
 ===================
-If you'll be using script-based authentication, you need to create a Script entity in ShotGrid. To create a new key, click the + button on the "Scripts" page in the Admin section and give your script a useful name. It's a good idea to add any other relevant information that be be helpful to your other friendly ShotGrid users such as a description of what the script does that is using this key, the email address of the maintainer, etc.:
+If you'll be using script-based authentication, you need to create a Script entity in Flow Production Tracking. To create a new key, click the + button on the "Scripts" page in the Admin section and give your script a useful name. It's a good idea to add any other relevant information that be be helpful to your other friendly Flow Production Tracking users such as a description of what the script does that is using this key, the email address of the maintainer, etc.:
 
 .. image:: images/scripts_page.png
 
-Once you save your new Script entity, ShotGrid will automatically generate an application key which will act as the script's password. The key will look something like this: ``0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef``.
+Once you save your new Script entity, Flow Production Tracking will automatically generate an application key which will act as the script's password. The key will look something like this: ``0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef``.
 
 Why have different application keys for different scripts?
 ==========================================================
@@ -42,24 +42,24 @@ We recommend you create a new Script entity (and application key) for each scrip
 
 Event Logging
 =============
-By default, events generated by scripts using an script-based authentication are logged in ShotGrid's event log. You can turn this off by un-checking the "Generate Events" checkbox either in the script detail page or from the main Scripts admin page in ShotGrid.
+By default, events generated by scripts using an script-based authentication are logged in Flow Production Tracking's event log. You can turn this off by un-checking the "Generate Events" checkbox either in the script detail page or from the main Scripts admin page in Flow Production Tracking.
 
 .. note:: Turning off event logging will also prevent any email notifications from being triggered by your scripts since the email notifier relies on the event log to find events to notify for.
 
-Scripts using user-based authentication will generate events similarly to if you were performing the same actions in the ShotGrid web application, though there is some additional metadata stored in the ``EventLogEntry`` that identifies the event as created from a script acting on behalf of the user.
+Scripts using user-based authentication will generate events similarly to if you were performing the same actions in the Flow Production Tracking web application, though there is some additional metadata stored in the ``EventLogEntry`` that identifies the event as created from a script acting on behalf of the user.
 
 Why would you want to turn event logging off for scripts?
 ---------------------------------------------------------
-It is an optimization that is not used often, but some users have integration scripts that are pushing data into ShotGrid just for reference, like publishes from their asset management system. This publish data is never changed later, so the data itself has the entire history, and the events would just clutter the event log. The event log can grow very large. So if you have no need to audit the history of what your script does, and it's generating an large amount of event log entries, you may find it's not necessary to create these events.
+It is an optimization that is not used often, but some users have integration scripts that are pushing data into Flow Production Tracking just for reference, like publishes from their asset management system. This publish data is never changed later, so the data itself has the entire history, and the events would just clutter the event log. The event log can grow very large. So if you have no need to audit the history of what your script does, and it's generating an large amount of event log entries, you may find it's not necessary to create these events.
 
 ***********
 Permissions
 ***********
-Users and scripts are both bound by the restrictions of their permission role in ShotGrid. The permission role is assigned by the **Permission Role** field for each entity type.
+Users and scripts are both bound by the restrictions of their permission role in Flow Production Tracking. The permission role is assigned by the **Permission Role** field for each entity type.
 
-For Scripts, the default permission role is "API Admin User" which allows full access to create, update, and delete entities and fields, including editing the "date created" audit field and creating event log entries. If you have other permission roles for ApiUsers, you can set the default role that will be assigned when a new script is created, in your ShotGrid site preferences.
+For Scripts, the default permission role is "API Admin User" which allows full access to create, update, and delete entities and fields, including editing the "date created" audit field and creating event log entries. If you have other permission roles for ApiUsers, you can set the default role that will be assigned when a new script is created, in your Flow Production Tracking site preferences.
 
-When using user-based authentication in your script, it will be bound by the permission role assigned to you in ShotGrid. For example, if you don't have access to edit the status field on Shots, your script won't be able to either. Attempting to perform actions that are prohibited by permissions will raise an appropriate exception.
+When using user-based authentication in your script, it will be bound by the permission role assigned to you in Flow Production Tracking. For example, if you don't have access to edit the status field on Shots, your script won't be able to either. Attempting to perform actions that are prohibited by permissions will raise an appropriate exception.
 
 .. seealso:: `Permissions Documentation <https://help.autodesk.com/view/SGSUB/ENU/?guid=SG_Administrator_ar_site_configuration_ar_permissions_html>`_
 
diff --git a/docs/cookbook.rst b/docs/cookbook.rst
index 756c44c5b..f69334a7b 100644
--- a/docs/cookbook.rst
+++ b/docs/cookbook.rst
@@ -29,7 +29,7 @@ and paste any of these into your own scripts.
 .. rubric:: Working With Files
 
 You'll probably be doing some work with files at your studio. This is a deep dive into some of 
-the inners of how ShotGrid handles files (also called Attachments) and the different ways to link
+the inners of how Flow Production Tracking handles files (also called Attachments) and the different ways to link
 to them.
 
 .. toctree::
@@ -39,9 +39,9 @@ to them.
 
 .. rubric:: Working With Tasks
 
-Scheduling is a complex beast. ShotGrid can handle lots of different types of functionality around
+Scheduling is a complex beast. Flow Production Tracking can handle lots of different types of functionality around
 scheduling like split tasks, dependencies, and more. These docs walk you through the details of
-how ShotGrid thinks when it's handling Task changes and how you can make your scripts do what you
+how Flow Production Tracking thinks when it's handling Task changes and how you can make your scripts do what you
 need to do.
 
 .. toctree::
@@ -52,7 +52,7 @@ need to do.
 .. rubric:: Smart Cut Fields
 
 Smart Cut Fields are deprecated in favor of the 
-`new cut support added in ShotGrid v7.0 <https://knowledge.autodesk.com/support/shotgrid/learn-explore/caas/CloudHelp/cloudhelp/ENU/SG-Editorial/files/SG-Editorial-ed-cut-schema-html-html.html>`_. 
+`new cut support added in ShotGrid v7.0 <https://knowledge.autodesk.com/support/shotgrid/learn-explore/caas/CloudHelp/cloudhelp/ENU/SG-Editorial/files/SG-Editorial-ed-cut-schema-html-html.html>`_.
 This documentation remains only to support studios who may not have upgraded to the new cut support
 features. 
 
diff --git a/docs/cookbook/attachments.rst b/docs/cookbook/attachments.rst
index 5e41f0bd6..e265071e8 100644
--- a/docs/cookbook/attachments.rst
+++ b/docs/cookbook/attachments.rst
@@ -4,26 +4,26 @@
 Details About Working With Files
 ################################
 
-The ShotGrid web application stores Files as Attachment entities. You can see these on a Files page,
+The Flow Production Tracking web application stores Files as Attachment entities. You can see these on a Files page,
 or a Files tab on a detail page, for example. You can access Attachments via the API to create and
 modify uploaded files, url links, and local files, and link them to other entities (Shots,
-Versions, etc). This entity works a lot like other entity types within ShotGrid with a few
+Versions, etc). This entity works a lot like other entity types within Flow Production Tracking with a few
 exceptions which are detailed below.
 
 .. note::
-    If you are simply looking for information about how to upload and link things in ShotGrid, this
+    If you are simply looking for information about how to upload and link things in Flow Production Tracking, this
     doc is not for you. Instead look at the :meth:`~shotgun_api3.Shotgun.upload` and
     :meth:`~shotgun_api3.Shotgun.upload_thumbnail` methods.
 
     This doc describes the detailed structure of the Attachment entities that represent files
-    in ShotGrid and how to interact with them. If that sounds cool too, then read on!
+    in Flow Production Tracking and how to interact with them. If that sounds cool too, then read on!
 
 .. versionadded:: 3.0.3
 
 *****************
 Default structure
 *****************
-The following is a list of the default fields that ShotGrid creates for Attachments. Your server
+The following is a list of the default fields that Flow Production Tracking creates for Attachments. Your server
 instance may look slightly different depending on your own customizations. Many of these fields are
 optional and some are automatically filled in. These exceptions are listed below in the
 descriptions of each field.
@@ -46,7 +46,7 @@ descriptions of each field.
     the size of the file in bytes.
 
 - **id** (:obj:`int`):
-    The internal ShotGrid id for this Attachment entity.
+    The internal Flow Production Tracking id for this Attachment entity.
 
 - **attachment_links** (:obj:`list`):
     A list of entity dictionaries used for linking Attachments to multiple entities.
@@ -74,7 +74,7 @@ descriptions of each field.
     List of tags (as strings) that are currently assigned to the Attachment.
 
 - **image** (:obj:`str`):
-    The url location of the thumbnail image assigned to this Attachment. For uploads, ShotGrid
+    The url location of the thumbnail image assigned to this Attachment. For uploads, Flow Production Tracking
     automatically tries to create a thumbnail from the file.
     See :ref:`interpreting_image_field_strings`. Alternatively, you can assign your
     own thumbnail to an Attachment using the :meth:`~shotgun_api3.Shotgun.upload_thumbnail` method.
@@ -94,8 +94,8 @@ Depending on the type of file the Attachment entity is representing, the value o
 will vary.
 
 - **Uploads**
-    Designated by ``link_type: 'upload'``, this represents a file that was uploaded to ShotGrid.
-    Uploading files to ShotGrid can be done using the :meth:`~shotgun_api3.Shotgun.upload` method.
+    Designated by ``link_type: 'upload'``, this represents a file that was uploaded to Flow Production Tracking.
+    Uploading files to Flow Production Tracking can be done using the :meth:`~shotgun_api3.Shotgun.upload` method.
     You cannot create an Attachment with an uploaded file directly.
 
     ::
@@ -174,14 +174,14 @@ Updating Attachments
 ********************
 You cannot modify the ``this_file`` field after you create an Attachment. If you need to provide a
 different file, you will have to create a new Attachment entity. Otherwise, the process for
-updating Attachments is exactly like updating other entity types in ShotGrid and is the same for all
+updating Attachments is exactly like updating other entity types in Flow Production Tracking and is the same for all
 Attachment types. See :meth:`~shotgun_api3.Shotgun.update` for more info.
 
 
 ********************
 Deleting Attachments
 ********************
-The process of deleting an Attachment is just like other entities in ShotGrid. See
+The process of deleting an Attachment is just like other entities in Flow Production Tracking. See
 :meth:`~shotgun_api3.Shotgun.delete` for more info.
 
 .. _local_files:
@@ -190,14 +190,14 @@ The process of deleting an Attachment is just like other entities in ShotGrid. S
 Working With Local File Types
 *****************************
 
-We added support for linking to local files in the UI in ShotGrid Server v2.1. This doc covers how
+We added support for linking to local files in the UI in Flow Production Tracking Server v2.1. This doc covers how
 to work with these local file links using the API.
 
 Requirements
 ============
 
 - Python API v3.0.3+
-- ShotGrid Server v2.1.10+
+- Flow Production Tracking Server v2.1.10+
 
 Structure of Local File Values
 ==============================
@@ -275,7 +275,7 @@ Returns::
 Creating & Updating Local file Fields
 =====================================
 
-When setting a file/link field value to a local file, only the ``local_path`` is mandatory. ShotGrid
+When setting a file/link field value to a local file, only the ``local_path`` is mandatory. Flow Production Tracking
 will automatically select the appropriate matching local storage for your file based on the path.
 You can optionally specify the ``name`` and ``content_type`` fields if you wish to override their
 defaults. Any other keys that are provided will be ignored.
@@ -289,7 +289,7 @@ defaults. Any other keys that are provided will be ignored.
     Optional display name of the local file. This is set to the filename by default.
 
 * **local_path** :obj:`str`:
-    The full local path to the file. ShotGrid will find the LocalStorage
+    The full local path to the file. Flow Production Tracking will find the LocalStorage
     that has the most specific match to this path and automatically assign that LocalStorage to
     the file.
 
@@ -315,7 +315,7 @@ Returns::
                             'url': 'file:///Users/kp/Movies/testing/test_movie_002.mov'},
      'type': 'Version'}]
 
-The ``content_type`` was assigned a best-guess value based on the file extension. ShotGrid selected
+The ``content_type`` was assigned a best-guess value based on the file extension. Flow Production Tracking selected
 the most appropriate specific LocalStorage match and assigned it to local_storage automatically.
 
 Un-setting local file field values
diff --git a/docs/cookbook/examples/ami_version_packager.rst b/docs/cookbook/examples/ami_version_packager.rst
index 3ac7917d0..5d3035014 100644
--- a/docs/cookbook/examples/ami_version_packager.rst
+++ b/docs/cookbook/examples/ami_version_packager.rst
@@ -20,7 +20,7 @@ It is intended to be used in conjunction with the script dicussed in :ref:`ami_h
     """
     version_packager.py
 
-    This example script is meant to be run from an ActionMenuItem in ShotGrid. The menu item uses a custom
+    This example script is meant to be run from an ActionMenuItem in Flow Production Tracking. The menu item uses a custom
     protocol in order to launch this script, and is followed by the action 'package4client'. So the full
     url would be something like launchme://package4client?.... See:
     https://developer.shotgridsoftware.com/python-api/cookbook/examples/ami_handler.html
@@ -29,9 +29,9 @@ It is intended to be used in conjunction with the script dicussed in :ref:`ami_h
     POST variables. For more information about it and accessing the variables in the ActionMenuItem POST request,
     See: http://developer.shotgridsoftware.com/python-api/examples/ami_handler
 
-    The purpose of this script is to download attachment files from ShotGrid, create an archive of them
+    The purpose of this script is to download attachment files from Flow Production Tracking, create an archive of them
     and copy them to a specified directory. You can invoke it with the following minimal example to connect
-    to ShotGrid, download any file that exists in the specified field ('sg_qt') for each selected_id passed from the 
+    to Flow Production Tracking, download any file that exists in the specified field ('sg_qt') for each selected_id passed from the
     ActionMenu. Then it will create a single archive of the files and move it to the specified directory
     ('/path/where/i/want/to/put/the/archive/'). The archive is named with the Project Name, timestamp, and user
     login who ran the ActionMenuItem ('Demo_Project_2010-04-29-172210_kp.tar.gz'):
@@ -59,7 +59,7 @@ It is intended to be used in conjunction with the script dicussed in :ref:`ami_h
     # ---------------------------------------------------------------------------------------------
     # Variables
     # ---------------------------------------------------------------------------------------------
-    # ShotGrid server auth info
+    # Flow Production Tracking server auth info
     shotgun_conf = {
         'url':'https://my-site.shotgrid.autodesk.com', 
         'name':'YOUR_SCRIPT_NAME_HERE', 
@@ -79,7 +79,7 @@ It is intended to be used in conjunction with the script dicussed in :ref:`ami_h
 
 
     # ----------------------------------------------
-    # Generic ShotGrid Exception Class
+    # Generic Flow Production Tracking Exception Class
     # ----------------------------------------------
     class ShotgunException(Exception):
         pass
@@ -125,7 +125,7 @@ It is intended to be used in conjunction with the script dicussed in :ref:`ami_h
         attachment_id = extract_attachment_id(attachment)
         if type(attachment_id) != int:
             return None
-        # download the attachment file from ShotGrid and write it to local disk
+        # download the attachment file from Flow Production Tracking and write it to local disk
         logger.info("Downloading Attachment #%s" % (attachment_id)) 
         stream = sg.download_attachment(attachment_id)
         try:
diff --git a/docs/cookbook/examples/basic_create_shot.rst b/docs/cookbook/examples/basic_create_shot.rst
index 5c70585cf..4a9ece5f6 100644
--- a/docs/cookbook/examples/basic_create_shot.rst
+++ b/docs/cookbook/examples/basic_create_shot.rst
@@ -27,7 +27,7 @@ This will create a new Shot named "100_010" in the Project "Gunslinger" (which h
 
 - ``data`` is a list of key/value pairs where the key is the column name to update and the value 
   is the the value to set.
-- ``sg`` is the ShotGrid API instance you created in :ref:`example_sg_instance`. 
+- ``sg`` is the Flow Production Tracking API instance you created in :ref:`example_sg_instance`.
 - ``create()`` is the :meth:`shotgun_api3.Shotgun.create` API method we are calling. We pass in the 
   entity type we're searching for and the data we're setting.
 
@@ -44,11 +44,11 @@ The variable ``result`` now contains a dictionary hash with the Shot information
         'type': 'Shot'
     }
 
-In addition, ShotGrid has returned the ``id`` that it has assigned to the Shot, as well as a 
+In addition, Flow Production Tracking has returned the ``id`` that it has assigned to the Shot, as well as a
 ``type`` value. ``type`` is provided for convenience simply to help you identify what entity type
-this dictionary represents. It does not correspond to any field in ShotGrid. 
+this dictionary represents. It does not correspond to any field in Flow Production Tracking.
 
-ShotGrid will *always* return the ``id`` and ``type`` keys in the dictionary when there are results
+Flow Production Tracking will *always* return the ``id`` and ``type`` keys in the dictionary when there are results
 representing an entity.
 
 The Complete Example
@@ -66,7 +66,7 @@ The Complete Example
     # --------------------------------------
     # Globals
     # --------------------------------------
-    # make sure to change this to match your ShotGrid server and auth credentials.
+    # make sure to change this to match your Flow Production Tracking server and auth credentials.
     SERVER_PATH = "https://my-site.shotgrid.autodesk.com" 
     SCRIPT_NAME = 'my_script'     
     SCRIPT_KEY = '27b65d7063f46b82e670fe807bd2b6f3fd1676c1'
diff --git a/docs/cookbook/examples/basic_create_shot_task_template.rst b/docs/cookbook/examples/basic_create_shot_task_template.rst
index 4144bf460..0fa3b0828 100644
--- a/docs/cookbook/examples/basic_create_shot_task_template.rst
+++ b/docs/cookbook/examples/basic_create_shot_task_template.rst
@@ -1,6 +1,6 @@
 Create a Shot with a Task Template
 ==================================
-Creating a new Shot with a Task Template is just like linking it to another entity, but ShotGrid will apply the Task Template in the background and create the appropriate Tasks on the Shot for you.
+Creating a new Shot with a Task Template is just like linking it to another entity, but Flow Production Tracking will apply the Task Template in the background and create the appropriate Tasks on the Shot for you.
 
 Find the Task Template
 ----------------------
@@ -31,7 +31,7 @@ Now we can create the Shot with the link to the ``TaskTemplate`` to apply.
     result = sg.create('Shot', data)
 
 This will create a new Shot named "100_010" linked to the TaskTemplate "3D Shot Template" and 
-ShotGrid will then create the Tasks defined in the template and link them to the Shot you just 
+Flow Production Tracking will then create the Tasks defined in the template and link them to the Shot you just
 created.
 
 - ``data`` is a list of key/value pairs where the key is the column name to update and the value is 
@@ -65,7 +65,7 @@ If we now search for the Tasks linked to the Shot, we'll find the Tasks that mat
     tasks = sg.find('Task', filters=[['entity', 'is', result]])
 
 .. note:: You can use an entity dictionary that was returned from the API in a filter as we have
-    done above. ShotGrid will only look at the ``id`` and ``type`` keys and will ignore the rest.
+    done above. Flow Production Tracking will only look at the ``id`` and ``type`` keys and will ignore the rest.
     This is a handy way to pass around entity dictionaries without having to reformat them.
 
 Now the ``tasks`` variable contains the following::
diff --git a/docs/cookbook/examples/basic_create_version_link_shot.rst b/docs/cookbook/examples/basic_create_version_link_shot.rst
index bdec9ef46..71e6f3e1e 100644
--- a/docs/cookbook/examples/basic_create_version_link_shot.rst
+++ b/docs/cookbook/examples/basic_create_version_link_shot.rst
@@ -1,6 +1,6 @@
 Create a Version Linked to a Shot
 =================================
-You've just created a sweet new Version of your shot. Now you want to update ShotGrid and create a 
+You've just created a sweet new Version of your shot. Now you want to update Flow Production Tracking and create a
 new ``Version`` entity linked to the Shot.
 
 Find the Shot
@@ -28,7 +28,7 @@ variable from the previous search) and the Task Name, which maps to the ``conten
 
 .. note:: Linking a Task to the Version is good practice. By doing so it is easy for users to see
     at what stage a particular Version was created, and opens up other possibilities for tracking 
-    in ShotGrid. We highly recommend doing this whenever possible.
+    in Flow Production Tracking. We highly recommend doing this whenever possible.
 
 Create the Version
 ------------------
diff --git a/docs/cookbook/examples/basic_delete_shot.rst b/docs/cookbook/examples/basic_delete_shot.rst
index 5041ee269..5275735d6 100644
--- a/docs/cookbook/examples/basic_delete_shot.rst
+++ b/docs/cookbook/examples/basic_delete_shot.rst
@@ -3,7 +3,7 @@ Delete A Shot
 
 Calling :meth:`~shotgun_api3.Shotgun.delete`
 --------------------------------------------
-Deleting an entity in ShotGrid is pretty straight-forward. No extraneous steps required.::
+Deleting an entity in Flow Production Tracking is pretty straight-forward. No extraneous steps required.::
 
     result = sg.delete("Shot", 40435) 
 
@@ -28,7 +28,7 @@ The Complete Example
     # --------------------------------------
     # Globals
     # --------------------------------------
-    # make sure to change this to match your ShotGrid server and auth credentials.
+    # make sure to change this to match your Flow Production Tracking server and auth credentials.
     SERVER_PATH = "https://my-site.shotgrid.autodesk.com"
     SCRIPT_NAME = 'my_script'     
     SCRIPT_KEY = '27b65d7063f46b82e670fe807bd2b6f3fd1676c1'
diff --git a/docs/cookbook/examples/basic_find_shot.rst b/docs/cookbook/examples/basic_find_shot.rst
index 19fed7cf9..88c8c81e0 100644
--- a/docs/cookbook/examples/basic_find_shot.rst
+++ b/docs/cookbook/examples/basic_find_shot.rst
@@ -14,7 +14,7 @@ Pretty simple right? Well here's a little more insight into what's going on.
 
 - ``filters`` is an list of filter conditions. In this example we are filtering for Shots where 
   the ``id`` column is **40435**.
-- ``sg`` is the ShotGrid API instance. 
+- ``sg`` is the Flow Production Tracking API instance.
 - ``find_one()`` is the :meth:`~shotgun_api3.Shotgun.find_one` API method we are calling. We
   provide it with the entity type we're searching for and our filters.
 
@@ -26,7 +26,7 @@ So what does this return? The variable result now contains::
     {'type': 'Shot','id': 40435}
 
 By default, :meth:`~shotgun_api3.Shotgun.find_one` returns a single dictionary object with 
-the ``type`` and ``id`` fields. So in this example, we found a Shot matching that id, and ShotGrid 
+the ``type`` and ``id`` fields. So in this example, we found a Shot matching that id, and Flow Production Tracking
 returned it as a dictionary object with ``type`` and ``id`` keys .
 
 How do we know that result contains the Shot dictionary object? You can trust us... but just to be 
@@ -52,7 +52,7 @@ The Complete Example
     # --------------------------------------
     # Globals
     # --------------------------------------
-    # make sure to change this to match your ShotGrid server and auth credentials.
+    # make sure to change this to match your Flow Production Tracking server and auth credentials.
     SERVER_PATH = "https://my-site.shotgrid.autodesk.com"
     SCRIPT_NAME = 'my_script'     
     SCRIPT_KEY = '27b65d7063f46b82e670fe807bd2b6f3fd1676c1'
diff --git a/docs/cookbook/examples/basic_sg_instance.rst b/docs/cookbook/examples/basic_sg_instance.rst
index fed8a6c51..b39c78432 100644
--- a/docs/cookbook/examples/basic_sg_instance.rst
+++ b/docs/cookbook/examples/basic_sg_instance.rst
@@ -1,11 +1,11 @@
 .. _example_sg_instance:
 
-Create a ShotGrid API instance
-=============================
+Create a Flow Production Tracking API instance
+==============================================
 
-This example shows you how to establish your initial connection to ShotGrid using script-based 
-authentication. ``sg`` represents your ShotGrid API instance. Be sure you've read 
-:ref:`Setting Up ShotGrid for API Access <setting_up_shotgrid>`.
+This example shows you how to establish your initial connection to Flow Production Tracking using script-based
+authentication. ``sg`` represents your Flow Production Tracking API instance. Be sure you've read
+:ref:`Setting Up Flow Production Tracking for API Access <setting_up_shotgrid>`.
 ::
 
     import pprint # Useful for debugging
@@ -22,5 +22,5 @@ authentication. ``sg`` represents your ShotGrid API instance. Be sure you've rea
     # sg connection object
     pprint.pprint([symbol for symbol in sorted(dir(sg)) if not symbol.startswith('_')])
 
-For further information on what you can do with this ShotGrid object you can read the 
+For further information on what you can do with this Flow Production Tracking object you can read the
 :ref:`API reference <apireference>`.
\ No newline at end of file
diff --git a/docs/cookbook/examples/basic_update_shot.rst b/docs/cookbook/examples/basic_update_shot.rst
index 5d1b4ff9b..52e57e70e 100644
--- a/docs/cookbook/examples/basic_update_shot.rst
+++ b/docs/cookbook/examples/basic_update_shot.rst
@@ -17,7 +17,7 @@ This will update the ``description`` and the ``sg_status_list`` fields for the S
 
 - ``data`` is a list of key/value pairs where the key is the field name to update and the value to
   update it to.
-- ``sg`` is the ShotGrid API instance. 
+- ``sg`` is the Flow Production Tracking API instance.
 - ``update()`` is the :meth:`shotgun_api3.Shotgun.update` API method we are calling. We provide it 
   with the entity type we're updating, the ``id`` of the entity, and the data we're updating it 
   with.
@@ -33,11 +33,11 @@ The variable ``result`` now contains the Shot object that with the updated value
         'id': 40435
     }
 
-In addition, ShotGrid has returned the ``id`` for the Shot, as well as a ``type`` value. ``type`` 
+In addition, Flow Production Tracking has returned the ``id`` for the Shot, as well as a ``type`` value. ``type``
 is provided for convenience simply to help you identify what entity type this dictionary represents. 
-It does not correspond to any field in ShotGrid. 
+It does not correspond to any field in Flow Production Tracking.
 
-ShotGrid will *always* return the ``id`` and ``type`` keys in the dictionary when there are results
+Flow Production Tracking will *always* return the ``id`` and ``type`` keys in the dictionary when there are results
 representing an entity.
 
 The Complete Example
@@ -55,7 +55,7 @@ The Complete Example
     # --------------------------------------
     # Globals
     # --------------------------------------
-    # make sure to change this to match your ShotGrid server and auth credentials.
+    # make sure to change this to match your Flow Production Tracking server and auth credentials.
     SERVER_PATH = "https://my-site.shotgrid.autodesk.com"
     SCRIPT_NAME = 'my_script'     
     SCRIPT_KEY = '27b65d7063f46b82e670fe807bd2b6f3fd1676c1'
diff --git a/docs/cookbook/examples/basic_upload_thumbnail_version.rst b/docs/cookbook/examples/basic_upload_thumbnail_version.rst
index ed8b51827..2ae399d5f 100644
--- a/docs/cookbook/examples/basic_upload_thumbnail_version.rst
+++ b/docs/cookbook/examples/basic_upload_thumbnail_version.rst
@@ -1,10 +1,10 @@
 Upload a Thumbnail for a Version
 ================================
 
-So you've created a new Version of a Shot, and you've updated ShotGrid, but now you want to upload a 
+So you've created a new Version of a Shot, and you've updated Flow Production Tracking, but now you want to upload a
 beauty frame to display as the thumbnail for your Version. We'll assume you already have the image 
 made (located on your machine at ``/v1/gun/s100/010/beauties/anim/100_010_animv1.jpg``) . And since 
-you've just created your Version in ShotGrid, you know its ``id`` is **214**.
+you've just created your Version in Flow Production Tracking, you know its ``id`` is **214**.
 
 .. note:: If you upload a movie file or image to the ``sg_uploaded_movie`` field and you have 
     transcoding enabled on your server (the default for hosted sites), a thumbnail will be
@@ -18,9 +18,9 @@ Upload the Image using :meth:`~shotgun_api3.Shotgun.upload_thumbnail`
     sg.upload_thumbnail("Version", 214, "/v1/gun/s100/010/beauties/anim/100_010_animv1.jpg")
 
 
-ShotGrid will take care of resizing the thumbnail for you. If something does go wrong, an exception 
+Flow Production Tracking will take care of resizing the thumbnail for you. If something does go wrong, an exception
 will be thrown and you'll see the error details.
 
 .. note:: The result returned by :meth:`~shotgun_api3.Shotgun.upload_thumbnail` is an integer 
-    representing the id of a special ``Attachment`` entity in ShotGrid. Working with Attachments
+    representing the id of a special ``Attachment`` entity in Flow Production Tracking. Working with Attachments
     is beyond the scope of this example. :)
\ No newline at end of file
diff --git a/docs/cookbook/examples/svn_integration.rst b/docs/cookbook/examples/svn_integration.rst
index c0c3730b5..9a877b322 100644
--- a/docs/cookbook/examples/svn_integration.rst
+++ b/docs/cookbook/examples/svn_integration.rst
@@ -4,10 +4,10 @@
 Subversion (SVN) Integration
 ############################
 
-Integrating ShotGrid with Subversion consists of two basic parts:  
+Integrating Flow Production Tracking with Subversion consists of two basic parts:
 
 - Setup a post-commit hook in Subversion.
-- Create a ShotGrid API script to create the Revision in ShotGrid. This script will be called by 
+- Create a Flow Production Tracking API script to create the Revision in Flow Production Tracking. This script will be called by
   the post-commit hook.
  
 ****************
@@ -21,7 +21,7 @@ To setup the post-commit hook:
   as a starting point for the real thing.
 - Create your very own executable script, and save it in the same ``hooks`` folder, name it 
   ``post-commit``, and give it executable permission.
-- In your ``post-commit`` script, invoke your ShotGrid API script.
+- In your ``post-commit`` script, invoke your Flow Production Tracking API script.
 
 If this is entirely new to you, we highly suggest reading up on the topic. O'Reilly has `a free 
 online guide for Subversion 1.5 and 1.6 
@@ -55,14 +55,14 @@ Explanation of selected lines
   our ``REPOS`` and ``REV`` values, first with the ``author``, and then with ``log`` subcommand.  
   These are actually the first two original lines of code - everything else to this point was 
   pre-written already in the ``post-commit.tmpl`` file. nice :)  
-- line ``10``: This is the absolute path to our ShotGrid API Script.
+- line ``10``: This is the absolute path to our Flow Production Tracking API Script.
 
-******************
-ShotGrid API Script
-******************
+***********************************
+Flow Production Tracking API Script
+***********************************
 
-This script will create the Revision and populate it with some metadata using the ShotGrid Python 
-API. It will create our Revision in ShotGrid along with the author, comment, and because we use 
+This script will create the Revision and populate it with some metadata using the Flow Production Tracking Python
+API. It will create our Revision in Flow Production Tracking along with the author, comment, and because we use
 Trac (a web-based interface for Subversion), it will also populate a URL field with a clickable 
 link to the Revision.
 
@@ -105,7 +105,7 @@ link to the Revision.
        # Set the Trac path for this specific revision
        revision_url = REVISIONS_PATH + revision_code
        
-       # Validate that author is a valid ShotGrid HumanUser
+       # Validate that author is a valid Flow Production Tracking HumanUser
        result = sg.find_one("HumanUser", [['login', 'is', author]])
        if result:
            # Create Revision
@@ -121,33 +121,33 @@ link to the Revision.
        
        # Send error message if valid HumanUser is not found
        else:
-           print("Unable to find valid ShotGrid User with login: "+author+", Revision not created in ShotGrid.")
+           print("Unable to find a valid Flow Production Tracking User with login: {}, Revision not created in Flow Production Tracking.".format(author))
 
 
 
 Explanation of selected lines:
 ==============================
 
-- line ``14``: This should be the URL to your instance of ShotGrid.
+- line ``14``: This should be the URL to your instance of Flow Production Tracking.
 - lines ``15-16``: Make sure you get these values from the "Scripts" page in the Admin section of
-  the ShotGrid web application. If you're not sure how to do this, check out :doc:`authentication`.
+  the Flow Production Tracking web application. If you're not sure how to do this, check out :doc:`authentication`.
 - line ``17``: This is the address of Trac, our web-based interface that we use with Subversion. 
   You may use a different interface, or none at all, so feel free to adjust this line or ignore it 
   as your case may be.
-- line ``18``: Every Revision in ShotGrid must have a Project, which is passed to the API as a 
+- line ``18``: Every Revision in Flow Production Tracking must have a Project, which is passed to the API as a
   dictionary with two keys, the ``type`` and the ``id``.  Of course the ``type`` value will always 
   remain ``Project`` (case sensitive), but the ``id`` will change by Project.  To find out the 
-  ``id`` of your Project, go to the Projects page in the ShotGrid web application, locate the 
+  ``id`` of your Project, go to the Projects page in the Flow Production Tracking web application, locate the
   Project where you want your Revisions created, and then locate its ``id`` field (which you may 
   need to display - if you don't see it, right click on any column header then select 
   "Insert Column" > "Id").  Note that for this example we assume that all Revisions in this 
   Subversion repository will belong to the same Project.
 - lines ``28-31``: Grab the values from the objects that were left for us in the environment.
 - line ``34``: Add the Revision number to complete the path of our Trac url.
-- line ``37``: Make sure that a valid User exists in ShotGrid.  In our example, we assume that our 
-  Users' ShotGrid logins match their Subversion names.  If the user exists in ShotGrid, that 
+- line ``37``: Make sure that a valid User exists in Flow Production Tracking.  In our example, we assume that our
+  Users' Flow Production Tracking logins match their Subversion names.  If the user exists in Flow Production Tracking, that
   user's ``id`` will be returned as ``result['id']``, which we will need later on in line 46.
-- lines ``40-48``: Use all the meta data we've gathered to create a Revision in ShotGrid. If none 
+- lines ``40-48``: Use all the meta data we've gathered to create a Revision in Flow Production Tracking. If none
   of these lines make any sense, check out more on the :meth:`~shotgun_api3.Shotgun.create` method 
   here.   Line 41 deserves special mention: notice that we define a dictionary called ``url`` that 
   has three important keys: ``content_type``, ``url``, and ``name``, and we then pass this in as 
@@ -164,7 +164,7 @@ My post-commit script is simply not running. I can run it manually, but commits
 Make sure that the script is has explicitly been made executable and that all users who will 
 invoke it have appropriate permissions for the script and that folders going back to root. 
 
-My ShotGrid API script is not getting called by the post-commit hook. 
-====================================================================
+My Flow Production Tracking API script is not getting called by the post-commit hook.
+=====================================================================================
 
 Make sure that the script is called using its absolute path.
diff --git a/docs/cookbook/smart_cut_fields.rst b/docs/cookbook/smart_cut_fields.rst
index 23d8669da..0ee74d189 100644
--- a/docs/cookbook/smart_cut_fields.rst
+++ b/docs/cookbook/smart_cut_fields.rst
@@ -5,7 +5,7 @@ Smart Cut Fields
 ################
 
 .. warning::
-    Smart Cut Fields should be considered deprecated. ShotGrid v7.0, introduced a new version of 
+    Smart Cut Fields should be considered deprecated. ShotGrid v7.0, introduced a new version of
     cut support. `Read the Cut Support Documentation here <https://knowledge.autodesk.com/support/shotgrid/learn-explore/caas/CloudHelp/cloudhelp/ENU/SG-Editorial/files/SG-Editorial-ed-cut-schema-html-html.html>`_.
 
 If you want to work with 'smart' cut fields through the API, your script should use a corresponding
diff --git a/docs/cookbook/tasks/split_tasks.rst b/docs/cookbook/tasks/split_tasks.rst
index ade069f99..45dfc303f 100644
--- a/docs/cookbook/tasks/split_tasks.rst
+++ b/docs/cookbook/tasks/split_tasks.rst
@@ -5,7 +5,7 @@ Split Tasks
 ###########
 
 Split tasks can be created and edited via the API but must comply to some rules. Before going 
-further, a good understanding of :ref:`how ShotGrid handles task dates is useful <updating_tasks>`.
+further, a good understanding of :ref:`how Flow Production Tracking handles task dates is useful <updating_tasks>`.
 
 ********
 Overview
diff --git a/docs/cookbook/tasks/task_dependencies.rst b/docs/cookbook/tasks/task_dependencies.rst
index 48a09e686..a5cfc20be 100644
--- a/docs/cookbook/tasks/task_dependencies.rst
+++ b/docs/cookbook/tasks/task_dependencies.rst
@@ -5,7 +5,7 @@ Task Dependencies
 #################
 
 Task dependencies work the same way in the API as they do in the UI. You can filter and sort on 
-any of the fields. For information about Task Dependencies in ShotGrid, check out the `main 
+any of the fields. For information about Task Dependencies in Flow Production Tracking, check out the `main
 documentation page on our support site 
 <https://help.autodesk.com/view/SGSUB/ENU/?guid=SG_Producer_pr_scheduling_tasks_pr_gantt_chart_tasks_html>`_
 
@@ -232,7 +232,7 @@ Our Tasks now look like this::
      ...  
 
 Because the "Anm" Task ``start_date`` depends on the ``due_date`` of the "Layout" Task, this 
-change creates a dependency violation. The update succeeds, but ShotGrid has also set the 
+change creates a dependency violation. The update succeeds, but Flow Production Tracking has also set the
 ``dependency_violation`` field to ``True`` and has also updated the ``pinned`` field to ``True``. 
 
 The ``pinned`` field simply means that if the upstream Task(s) are moved, the "Anm" Task will no 
@@ -315,7 +315,7 @@ Updating the ``pinned`` field on a Task with a Dependency Violation
 
 Let's go back a couple of steps to where our "Anm" Task had a Dependency Violation because we had 
 moved the Start Date up before the "Layout" Task End Date. Remember that the ``pinned`` field 
-was also ``True``. If we simply update the ``pinned`` field to be ``False``, ShotGrid will also 
+was also ``True``. If we simply update the ``pinned`` field to be ``False``, Flow Production Tracking will also
 automatically update the Task dates to satisfy the upstream dependencies and reset the 
 ``dependency_violation`` value to ``False``::
 
@@ -349,7 +349,7 @@ Our Tasks now look like this::
     ...  
 
 
-Notice by updating ``pinned`` to ``False``, ShotGrid also updated the ``start_date`` and 
+Notice by updating ``pinned`` to ``False``, Flow Production Tracking also updated the ``start_date`` and
 ``due_date`` fields of our "Anm" Task so it will satisfy the upstream Task dependencies. And since 
 that succeeded, the ``dependency_violation`` field has also been set to ``False``
 
diff --git a/docs/cookbook/tasks/updating_tasks.rst b/docs/cookbook/tasks/updating_tasks.rst
index 3f8f9d5b7..97eb8c7b7 100644
--- a/docs/cookbook/tasks/updating_tasks.rst
+++ b/docs/cookbook/tasks/updating_tasks.rst
@@ -1,11 +1,11 @@
 .. _updating_tasks:
 
-#######################################
-Updating Task Dates: How ShotGrid Thinks
-#######################################
+########################################################
+Updating Task Dates: How Flow Production Tracking Thinks
+########################################################
 
 When updating Task dates in an API update() request, there is no specified order to the values that 
-are passed in. ShotGrid also does automatic calculation of the``start_date``,``due_date``, and ``duration`` fields for convenience. In order to clarify how updates are handled by ShotGrid we are 
+are passed in. Flow Production Tracking also does automatic calculation of the``start_date``,``due_date``, and ``duration`` fields for convenience. In order to clarify how updates are handled by Flow Production Tracking we are
 providing some general rules below and examples of what will happen when you make updates to your 
 Tasks.
 
@@ -16,12 +16,12 @@ General Rules
 - Updating the ``start_date`` automatically updates the ``due_date`` (``duration`` remains constant)
 - Updating the ``due_date`` automatically updates the ``duration`` (``start_date`` remains constant)
 - Updating the ``duration`` automatically updates the ``due_date`` (``start_date`` remains constant)
-- When updating Task values, ShotGrid sets schedule fields (``milestone``, ``duration``, 
+- When updating Task values, Flow Production Tracking sets schedule fields (``milestone``, ``duration``,
   ``start_date``, ``due_date``) after all other fields, because the Project and Task Assignees 
   affect schedule calculations.
 - If ``start_date`` and ``due_date`` are both set, ``duration`` is ignored (``duration`` can often 
   be wrong since it's easy to calculate scheduling incorrectly).
-- If both ``start_date`` and ``due_date`` are provided, ShotGrid sets ``start_date`` before 
+- If both ``start_date`` and ``due_date`` are provided, Flow Production Tracking sets ``start_date`` before
   ``due_date``.
 - Set ``milestone`` before other schedule fields (because ``start_date``, ``due_date``, and 
   ``duration`` get lost if ``milestone`` is not set to ``False`` first)
@@ -39,7 +39,7 @@ Examples
 The following examples show what the resulting Task object will look like after being run on the 
 initial Task object listed under the header of each section.
 
-The ``duration`` values in the following examples assume your ShotGrid instance is set to 
+The ``duration`` values in the following examples assume your Flow Production Tracking instance is set to
 10-hour work days. If your server is configured with a different setting, the ``duration`` values 
 will vary. 
 
diff --git a/docs/cookbook/tutorials.rst b/docs/cookbook/tutorials.rst
index 18235db89..99f56da02 100644
--- a/docs/cookbook/tutorials.rst
+++ b/docs/cookbook/tutorials.rst
@@ -3,7 +3,7 @@ Examples
 ########
 
 Here's a list of various simple tutorials to walk through that should provide you with a good base 
-understanding of how to use the ShotGrid API and what you can do with it.
+understanding of how to use the Flow Production Tracking API and what you can do with it.
 
 *****
 Basic
diff --git a/docs/cookbook/usage_tips.rst b/docs/cookbook/usage_tips.rst
index 389eb5227..620a96426 100644
--- a/docs/cookbook/usage_tips.rst
+++ b/docs/cookbook/usage_tips.rst
@@ -2,7 +2,7 @@
 API Usage Tips
 ##############
 
-Below is a list of helpful tips when using the ShotGrid API. We have tried to make the API very 
+Below is a list of helpful tips when using the Flow Production Tracking API. We have tried to make the API very
 simple to use with predictable results while remaining a powerful tool to integrate with your 
 pipeline. However, there's always a couple of things that crop up that our users might not be 
 aware of. Those are the types of things you'll find below. We'll be adding to this document over 
@@ -28,7 +28,7 @@ Don't::
 ***************
 Multi-threading
 ***************
-The ShotGrid API is not thread-safe. If you want to do threading we strongly suggest that you use 
+The Flow Production Tracking API is not thread-safe. If you want to do threading we strongly suggest that you use
 one connection object per thread and not share the connection.
 
 .. _entity-fields:
@@ -105,7 +105,7 @@ example of a field that resides on the connection entity between Playlists and V
 connection entity is appropriately called `PlaylistVersionConnection`. Because any Version can 
 exist in multiple Playlists, the sort order isn't specific to the Version, it's specific to 
 each _instance_ of the Version in a Playlist. These instances are tracked using connection 
-entities in Shtogun and are accessible just like any other entity type in ShotGrid.
+entities in Shtogun and are accessible just like any other entity type in Flow Production Tracking.
 
 To find information about your Versions in the Playlist "Director Review" (let's say it has an 
 ``id`` of 4). We'd run a query like so::
@@ -175,9 +175,9 @@ We can pull in field values from the linked Playlist and Version entities using
 entity. The field we are interested on the Version is ``code``. Put those together with our f
 riend the dot and we have ``version.Version.code``.
 
-*******************************************
-ShotGrid UI fields not available via the API
-*******************************************
+************************************************************
+Flow Production Tracking UI fields not available via the API
+************************************************************
 
 Summary type fields like Query Fields and Pipeline Step summary fields are currently only available 
 via the UI. Some other fields may not work as expected through the API because they are "display 
@@ -244,14 +244,14 @@ To see the logging output in stdout, define a streamhandler in your script::
     import shotgun_api3 as shotgun
     logging.basicConfig(level=logging.DEBUG)
 
-To write logging output from the ShotGrid API to a file, define a file handler in your script::
+To write logging output from the Flow Production Tracking API to a file, define a file handler in your script::
 
     import logging
     import shotgun_api3 as shotgun
     logging.basicConfig(level=logging.DEBUG, filename='/path/to/your/log')
 
 To suppress the logging output from the API in a script which uses logging, set the level of the 
-ShotGrid logger to a higher level::
+Flow Production Tracking logger to a higher level::
 
     import logging
     import shotgun_api3 as shotgun
@@ -267,7 +267,7 @@ Optimizations
 Combining Related Queries
 =========================
 Reducing round-trips for data via the API can significantly improve the speed of your application.
-Much like "Bubble Fields" / "Field Hopping" in the UI, we can poll ShotGrid for data on the fields
+Much like "Bubble Fields" / "Field Hopping" in the UI, we can poll Flow Production Tracking for data on the fields
 of entities linked to our main query, both as a part of the query parameters as well as in the
 data returned.
 
diff --git a/docs/images/scripts_page.png b/docs/images/scripts_page.png
index fdbc3c38d..d53da1cac 100644
Binary files a/docs/images/scripts_page.png and b/docs/images/scripts_page.png differ
diff --git a/docs/index.rst b/docs/index.rst
index 177453e46..5eef5a61c 100644
--- a/docs/index.rst
+++ b/docs/index.rst
@@ -1,21 +1,21 @@
-###################
-ShotGrid Python API3
-###################
+####################################
+Flow Production Tracking Python API3
+####################################
 Release |version|. (:ref:`Installation <installation>`)
 
 .. image:: https://img.shields.io/badge/shotgun-api-blue.svg
 
 
 
-ShotGrid provides a simple Python-based API for accessing ShotGrid and integrating with other tools.
-The ShotGrid API allows users to integrate their tools with ShotGrid very easily. Using this simple
-but powerful python module , you can quickly get your scripts integrated with ShotGrid's CRUD-based
+Flow Production Tracking provides a simple Python-based API for accessing Flow Production Tracking and integrating with other tools.
+The Flow Production Tracking API allows users to integrate their tools with Flow Production Tracking very easily. Using this simple
+but powerful python module , you can quickly get your scripts integrated with Flow Production Tracking's CRUD-based
 API.
 
 Because the needs of every studio can prove to be very different, we don't include a lot of
 "automation" or "smarts" in our API. We have kept it pretty low-level and leave most of those
 decisions to you. The API is powerful enough you can write your own "smarts" in a wrapper on top
-of the ShotGrid API.
+of the Flow Production Tracking API.
 
 .. _pythonoverviewvideo:
 
diff --git a/docs/installation.rst b/docs/installation.rst
index c40f61560..b082b1669 100644
--- a/docs/installation.rst
+++ b/docs/installation.rst
@@ -9,10 +9,10 @@ Minimum Requirements
 - Python 3.7
 
 .. note::
-    Some features of the API are only supported by more recent versions of the ShotGrid server.
+    Some features of the API are only supported by more recent versions of the Flow Production Tracking server.
     These features are added to the Python API in a backwards compatible way so that existing
     scripts will continue to function as expected. Accessing a method that is not supported for
-    your version of ShotGrid will raise an appropriate exception. In general, we attempt to
+    your version of Flow Production Tracking will raise an appropriate exception. In general, we attempt to
     document these where possible.
 
 ******************************
diff --git a/docs/reference.rst b/docs/reference.rst
index e7558f65c..c4da96caf 100644
--- a/docs/reference.rst
+++ b/docs/reference.rst
@@ -26,9 +26,9 @@ Shotgun()
 .. autoclass:: Shotgun
     :show-inheritance:
 
-***************
-ShotGrid Methods
-***************
+********************************
+Flow Production Tracking Methods
+********************************
 
 The majority of functionality is contained within the :class:`~shotgun_api3.Shotgun` class. 
 The documentation for all of the methods you'll need in your scripts lives in here.
@@ -91,7 +91,7 @@ The documentation for all of the methods you'll need in your scripts lives in he
     Shotgun.followers
     Shotgun.following
 
-.. rubric:: Working with the ShotGrid Schema and Preferences
+.. rubric:: Working with the Flow Production Tracking Schema and Preferences
 
 .. autosummary:: 
     :nosignatures:
@@ -109,7 +109,7 @@ The documentation for all of the methods you'll need in your scripts lives in he
 Connection & Authentication
 ===========================
 
-These methods are used for connecting and authenticating with your ShotGrid server. Most of 
+These methods are used for connecting and authenticating with your Flow Production Tracking server. Most of
 this is done automatically when you instantiate your instance. But if you need finer-grain
 control, these methods are available.
 
@@ -169,7 +169,7 @@ Methods that handle uploading and downloading files including thumbnails.
 Activity Stream
 ===============
 
-Methods that relate to the activity stream and following of entities in ShotGrid.
+Methods that relate to the activity stream and following of entities in Flow Production Tracking.
 
 .. automethod:: Shotgun.activity_stream_read
 .. automethod:: Shotgun.follow
@@ -177,10 +177,10 @@ Methods that relate to the activity stream and following of entities in ShotGrid
 .. automethod:: Shotgun.followers
 .. automethod:: Shotgun.following
 
-Working with the ShotGrid Schema
-===============================
+Working with the Flow Production Tracking Schema
+================================================
 
-Methods allow you to introspect and modify the ShotGrid schema.
+Methods allow you to introspect and modify the Flow Production Tracking schema.
 
 .. automethod:: Shotgun.schema_entity_read
 .. automethod:: Shotgun.schema_field_read
@@ -195,7 +195,7 @@ Methods allow you to introspect and modify the ShotGrid schema.
 Exceptions
 **********
 
-These are the various exceptions that the ShotGrid API will raise. 
+These are the various exceptions that the Flow Production Tracking API will raise.
 
 .. autoclass:: shotgun_api3.ShotgunError
     :show-inheritance:
@@ -479,7 +479,7 @@ Valid Operators By Data Type
 Additional Filter Presets
 =========================
 
-As of ShotGrid version 7.0 it is possible to also use filter presets. These presets provide a simple 
+As of Flow Production Tracking version 7.0 it is possible to also use filter presets. These presets provide a simple
 way to specify powerful query filters that would otherwise be costly and difficult to craft using 
 traditional filters.
 
@@ -651,7 +651,7 @@ date_time
 :range: Year must be >= 1970
 
     .. note::
-        Datetimes are stored as UTC on the server. The ShotGrid API is configured to automatically
+        Datetimes are stored as UTC on the server. The Flow Production Tracking API is configured to automatically
         convert between client local time and UTC. This can be overridden.
 
 duration
@@ -852,15 +852,15 @@ There are three possible states for values returned by an ``image`` field:
 Event Types
 ***********
 
-Whenever a user makes a change to any data in ShotGrid, an event log entry record is created, 
-capturing the value before and after. ShotGrid also logs some additional useful events that help keep 
-track of various activity on your ShotGrid instance.
+Whenever a user makes a change to any data in Flow Production Tracking, an event log entry record is created,
+capturing the value before and after. Flow Production Tracking also logs some additional useful events that help keep
+track of various activity on your Flow Production Tracking instance.
 
 Event-based Triggers
 ====================
 
 Events are particularlly useful when used in conjunction with a trigger framework like the
-`ShotGrid Event Daemon <https://github.com/shotgunsoftware/shotgunEvents>`_. This allows you to 
+`Flow Production Tracking Event Daemon <https://github.com/shotgunsoftware/shotgunEvents>`_. This allows you to
 write plug-ins that watch for certain types of events and then run code when they occur.
    
 Structure of Event Types
@@ -870,11 +870,11 @@ The basic structure of event types is broken into 3 parts:
 
 ``Application_EntityType_Action``
 
-- ``Application``: Is always "Shotgun" for events automatically created by the ShotGrid server. 
-  Other ShotGrid products may use their name in here, for example, Toolkit has its own events
+- ``Application``: Is always "Shotgun" for events automatically created by the Flow Production Tracking server.
+  Other Flow Production Tracking products may use their name in here, for example, Toolkit has its own events
   that it logs and the application portion is identified by "Toolkit". If you decide to use the 
   EventLogEntry entity to log events for your scripts or tools, you would use your tool name here.
-- ``EntityType``: This is the entity type in ShotGrid that was acted upon (eg. Shot, Asset, etc.)
+- ``EntityType``: This is the entity type in Flow Production Tracking that was acted upon (eg. Shot, Asset, etc.)
 - ``Action``: The general action that was taken. (eg. New, Change, Retirement, Revival)   
    
 
@@ -892,14 +892,14 @@ deleted, and revived. They follow this pattern:
 Additional Event Types
 ======================
 
-These are _some_ of the additional event types that are logged by ShotGrid:
+These are _some_ of the additional event types that are logged by Flow Production Tracking:
  
 - ``Shotgun_Attachment_View``: an Attachment (file) was viewed by a user.
 - ``Shotgun_Reading_Change``: a threaded entity has been marked read or unread. For example, a 
   Note was read by a user. The readings are unique to the entity<->user connection so when a 
   Note is read by user "joe" it may still be unread by user "jane".
-- ``Shotgun_User_Login``: a user logged in to ShotGrid.
-- ``Shotgun_User_Logout``: a user logged out of ShotGrid. 
+- ``Shotgun_User_Login``: a user logged in to Flow Production Tracking.
+- ``Shotgun_User_Logout``: a user logged out of Flow Production Tracking.
    
 
 Custom Event Types
@@ -907,10 +907,10 @@ Custom Event Types
 
 Since ``EventLogEntries`` are entities themselves, you can create them using the API just like any 
 other entity type. As mentioned previously, if you'd like to have your scripts or tools log to 
-the ShotGrid event log, simply devise a thoughtful naming structure for your event types and 
+the Flow Production Tracking event log, simply devise a thoughtful naming structure for your event types and
 create the EventLogEntry as needed following the usual methods for creating entities via the API.
 
-Again, other ShotGrid products like Toolkit use event logs this way.
+Again, other Flow Production Tracking products like Toolkit use event logs this way.
 
 .. note:: 
     EventLogEntries cannot be updated or deleted (that would defeat the purpose of course).   
@@ -918,13 +918,13 @@ Again, other ShotGrid products like Toolkit use event logs this way.
 Performance
 ===========
 
-Event log database tables can get large very quickly. While ShotGrid does very well with event logs 
+Event log database tables can get large very quickly. While Flow Production Tracking does very well with event logs
 that get into the millions of records, there's an inevitable degradation of performance for pages 
 that display them in the web application as well as any API queries for events when they get too 
 big. This volume of events is not the norm, but can be reached if your server expereinces high 
 usage. 
 
-This **does not** mean your ShotGrid server performance will suffer in general, just any pages that 
+This **does not** mean your Flow Production Tracking server performance will suffer in general, just any pages that
 are specifically displaying EventLogEntries in the web application, or API queries on the event
 log that are run. We are always looking for ways to improve this in the future. If you have any
 immediate concerns, please `reach out to our support team <https://www.autodesk.com/support/contact-support>`_
@@ -953,7 +953,7 @@ In the case that both this environment variable and the config's ``rpc_attempt_i
 Localization
 ************
 
-The ShotGrid API offers the ability to return localized display names in the current user's language.
+The Flow Production Tracking API offers the ability to return localized display names in the current user's language.
 Requests made from script/API users are localized in the site settings.
 
 This functionality is currently supported by the methods ``Shotgun.schema_entity_read``, ``Shotgun.schema_field_read``, and ``Shotgun.schema_read``.
diff --git a/setup.py b/setup.py
index 93a9de948..a2624aea6 100644
--- a/setup.py
+++ b/setup.py
@@ -28,9 +28,9 @@
 setup(
     name='shotgun_api3',
     version='3.4.2',
-    description='ShotGrid Python API ',
+    description='Flow Production Tracking Python API ',
     long_description=readme,
-    author='ShotGrid Software',
+    author='Autodesk',
     author_email='https://www.autodesk.com/support/contact-support',
     url='https://github.com/shotgunsoftware/python-api',
     license=license,
diff --git a/shotgun_api3/lib/README.md b/shotgun_api3/lib/README.md
index e8fc31cd6..1bdec6f78 100644
--- a/shotgun_api3/lib/README.md
+++ b/shotgun_api3/lib/README.md
@@ -6,7 +6,7 @@ Some third-party modules are bundled with `python-api` inside lib.
 
 ### httplib2
 
-`httplib2` is used to make http connections to the ShotGrid server.  We bundle both python2 and python3 compatible versions since httplib2 chose to maintain parallel versions of the module for python 2 and 3 compatibility.
+`httplib2` is used to make http connections to the Flow Production Tracking server.  We bundle both python2 and python3 compatible versions since httplib2 chose to maintain parallel versions of the module for python 2 and 3 compatibility.
 
 The version of `httplib2` bundled should be updated manually, however its version is included in the unused `shotgun_api3/lib/requirements.txt` to allow Github's automated CVE notifications to work.
 
@@ -29,7 +29,7 @@ Six is a Python 2/3 compatibility library.  In python-api, it's used to make sim
 
 The version of `six` bundled should be updated manually, however its version is included in the unused `shotgun_api3/lib/requirements.txt` to allow Github's automated CVE notifications to work.
 
-## ShotGrid Modules
+## Flow Production Tracking Modules
 
 ### sgsix
 
@@ -41,15 +41,15 @@ The version of `six` bundled should be updated manually, however its version is
 
 ### mockgun
 
-Mockgun is a ShotGrid API mocker. It's a class that has got *most* of the same
-methods and parameters that the ShotGrid API has got. Mockgun is essentially a
-ShotGrid *emulator* that (for basic operations) looks and feels like ShotGrid.
+Mockgun is a Flow Production Tracking API mocker. It's a class that has got *most* of the same
+methods and parameters that the Flow Production Tracking API has got. Mockgun is essentially a
+Flow Production Tracking *emulator* that (for basic operations) looks and feels like Flow Production Tracking.
 
 The primary purpose of Mockgun is to drive unit test rigs where it becomes
-too slow, cumbersome or non-practical to connect to a real ShotGrid. Using a
+too slow, cumbersome or non-practical to connect to a real Flow Production Tracking. Using a
 Mockgun for unit tests means that a test can be rerun over and over again
 from exactly the same database state. This can be hard to do if you connect
-to a live ShotGrid instance.
+to a live Flow Production Tracking instance.
 
 ## Lib `requirements.txt`
 
diff --git a/shotgun_api3/lib/mockgun/mockgun.py b/shotgun_api3/lib/mockgun/mockgun.py
index eab05f88d..fbe7ff085 100644
--- a/shotgun_api3/lib/mockgun/mockgun.py
+++ b/shotgun_api3/lib/mockgun/mockgun.py
@@ -201,7 +201,7 @@ def __init__(self,
         if schema_path is None or schema_entity_path is None:
             raise MockgunError("Cannot create Mockgun instance because no schema files have been defined. "
                                "Before creating a Mockgun instance, please call Mockgun.set_schema_paths() "
-                               "in order to specify which ShotGrid schema Mockgun should operate against.")
+                               "in order to specify which Flow Production Tracking schema Mockgun should operate against.")
 
         self._schema, self._schema_entity = SchemaFactory.get_schemas(schema_path, schema_entity_path)
 
@@ -504,7 +504,7 @@ def _validate_entity_data(self, entity_type, data):
                                    "url": dict}[sg_type]
                 except KeyError:
                     raise ShotgunError(
-                        "Field %s.%s: Handling for ShotGrid type %s is not implemented" %
+                        "Field %s.%s: Handling for Flow Production Tracking type %s is not implemented" %
                         (entity_type, field, sg_type)
                     )
 
diff --git a/shotgun_api3/shotgun.py b/shotgun_api3/shotgun.py
index 2ec07823a..4a55145ab 100644
--- a/shotgun_api3/shotgun.py
+++ b/shotgun_api3/shotgun.py
@@ -224,10 +224,10 @@ def __init__(self, host, meta):
         except AttributeError:
             self.version = None
         if not self.version:
-            raise ShotgunError("The ShotGrid Server didn't respond with a version number. "
+            raise ShotgunError("The Flow Production Tracking Server didn't respond with a version number. "
                                "This may be because you are running an older version of "
-                               "ShotGrid against a more recent version of the ShotGrid API. "
-                               "For more information, please contact ShotGrid Support.")
+                               "Flow Production Tracking against a more recent version of the Flow Production Tracking API. "
+                               "For more information, please contact the Autodesk support.")
 
         if len(self.version) > 3 and self.version[3] == "Dev":
             self.is_dev = True
@@ -339,7 +339,7 @@ class ClientCapabilities(object):
 
     :ivar str platform: The current client platform. Valid values are ``mac``, ``linux``,
         ``windows``, or ``None`` (if the current platform couldn't be determined).
-    :ivar str local_path_field: The SG field used for local file paths. This is calculated using
+    :ivar str local_path_field: The PTR field used for local file paths. This is calculated using
         the value of ``platform``. Ex. ``local_path_mac``.
     :ivar str py_version: Simple version of Python executable as a string. Eg. ``2.7``.
     :ivar str ssl_version: Version of OpenSSL installed. Eg. ``OpenSSL 1.0.2g  1 Mar 2016``. This
@@ -3441,8 +3441,8 @@ def _call_rpc(self, method, params, include_auth_params=True, first=False):
             except ProtocolError as e:
                 e.headers = resp_headers
 
-                # We've seen some rare instances of SG returning 502 for issues that
-                # appear to be caused by something internal to SG. We're going to
+                # We've seen some rare instances of PTR returning 502 for issues that
+                # appear to be caused by something internal to PTR. We're going to
                 # allow for limited retries for those specifically.
                 if attempt != max_attempts and e.errcode in [502, 504]:
                     LOG.debug("Got a 502 or 504 response. Waiting and retrying...")
@@ -3679,7 +3679,7 @@ def _parse_http_status(self, status):
         if status[0] >= 300:
             headers = "HTTP error from server"
             if status[0] == 503:
-                errmsg = "ShotGrid is currently down for maintenance or too busy to reply. Please try again later."
+                errmsg = "Flow Production Tracking is currently down for maintenance or too busy to reply. Please try again later."
             raise ProtocolError(self.config.server,
                                 error_code,
                                 errmsg,
@@ -3765,12 +3765,12 @@ def _response_errors(self, sg_response):
                 raise UserCredentialsNotAllowedForSSOAuthenticationFault(
                     sg_response.get("message",
                                     "Authentication using username/password is not "
-                                    "allowed for an SSO-enabled ShotGrid site")
+                                    "allowed for an SSO-enabled Flow Production Tracking site")
                 )
             elif sg_response.get("error_code") == ERR_OXYG:
                 raise UserCredentialsNotAllowedForOxygenAuthenticationFault(
                     sg_response.get("message", "Authentication using username/password is not "
-                                    "allowed for an Autodesk Identity enabled ShotGrid site")
+                                    "allowed for an Autodesk Identity enabled Flow Production Tracking site")
                 )
             else:
                 # raise general Fault
diff --git a/software_credits b/software_credits
index aa6e87c5c..819f81ee6 100644
--- a/software_credits
+++ b/software_credits
@@ -1,4 +1,4 @@
-The ShotGrid Python API uses the following software. Thanks to their creators, license information below.
+The Flow Production Tracking Python API uses the following software. Thanks to their creators, license information below.
 
 ============================== PYTHON ==============================
 
diff --git a/tests/base.py b/tests/base.py
index 5f4b61aa0..01b39bd15 100644
--- a/tests/base.py
+++ b/tests/base.py
@@ -1,4 +1,4 @@
-"""Base class for ShotGrid API tests."""
+"""Base class for Flow Production Tracking API tests."""
 import contextlib
 import os
 import random
@@ -152,7 +152,7 @@ def _setup_mock(self, s3_status_code_error=503):
                                                   {"version": [2, 4, 0]})
 
     def _mock_http(self, data, headers=None, status=None):
-        """Setup a mock response from the SG server.
+        """Setup a mock response from the PTR server.
 
         Only has an affect if the server has been mocked.
         """
diff --git a/tests/example_config b/tests/example_config
index 01501d23d..064eaba6a 100644
--- a/tests/example_config
+++ b/tests/example_config
@@ -13,7 +13,7 @@
 
 [SERVER_INFO]
 
-# Full url to the ShotGrid server server
+# Full url to the Flow Production Tracking server
 # e.g. https://my-site.shotgrid.autodesk.com
 # be careful to not end server_url with a "/", or some tests may fail
 server_url     : http://0.0.0.0:3000
@@ -24,7 +24,7 @@ http_proxy     :
 session_uuid   :
 
 [TEST_DATA]
-project_name   : SG unittest project
+project_name   : PTR unittest project
 
 human_name     : Sg unittest human
 human_login    : sgunittesthuman
diff --git a/tests/mockgun/schema.pickle b/tests/mockgun/schema.pickle
index 20ef8ee02..affaa8aba 100644
--- a/tests/mockgun/schema.pickle
+++ b/tests/mockgun/schema.pickle
@@ -86870,7 +86870,7 @@ p42730
 I01
 sS'value'
 p42731
-S'File field to contain the uploaded movie file. Used for playback of lower resolution movie media stored in ShotGrid.'
+S'File field to contain the uploaded movie file. Used for playback of lower resolution movie media stored in Flow Production Tracking.'
 p42732
 sssS'user'
 p42733
diff --git a/tests/test_api.py b/tests/test_api.py
index be3201fd6..4fdaab038 100644
--- a/tests/test_api.py
+++ b/tests/test_api.py
@@ -1737,7 +1737,7 @@ def test_following(self):
         '''Test following method'''
 
         if not self.sg.server_caps.version or self.sg.server_caps.version < (7, 0, 12):
-            warnings.warn("Test bypassed because SG server used does not support this feature.", FutureWarning)
+            warnings.warn("Test bypassed because PTR server used does not support this feature.", FutureWarning)
             return
 
         with self.gen_entity(
@@ -2607,7 +2607,7 @@ class TestReadAdditionalFilterPresets(base.LiveTestBase):
 
     def test_simple_case(self):
         if self.sg_version < (7, 0, 0):
-            warnings.warn("Test bypassed because SG server used does not support this feature.", FutureWarning)
+            warnings.warn("Test bypassed because PTR server used does not support this feature.", FutureWarning)
             return
 
         filters = [
@@ -2626,7 +2626,7 @@ def test_simple_case(self):
 
     def test_find_one(self):
         if self.sg_version < (7, 0, 0):
-            warnings.warn("Test bypassed because SG server used does not support this feature.", FutureWarning)
+            warnings.warn("Test bypassed because PTR server used does not support this feature.", FutureWarning)
             return
 
         filters = [
@@ -2644,7 +2644,7 @@ def test_find_one(self):
 
     def test_filter_with_no_name(self):
         if self.sg_version < (7, 0, 0):
-            warnings.warn("Test bypassed because SG server used does not support this feature.", FutureWarning)
+            warnings.warn("Test bypassed because PTR server used does not support this feature.", FutureWarning)
             return
 
         filters = [
@@ -2662,7 +2662,7 @@ def test_filter_with_no_name(self):
 
     def test_invalid_filter(self):
         if self.sg_version < (7, 0, 0):
-            warnings.warn("Test bypassed because SG server used does not support this feature.", FutureWarning)
+            warnings.warn("Test bypassed because PTR server used does not support this feature.", FutureWarning)
             return
 
         filters = [
@@ -2680,7 +2680,7 @@ def test_invalid_filter(self):
 
     def test_filter_not_iterable(self):
         if self.sg_version < (7, 0, 0):
-            warnings.warn("Test bypassed because SG server used does not support this feature.", FutureWarning)
+            warnings.warn("Test bypassed because PTR server used does not support this feature.", FutureWarning)
             return
 
         filters = [
@@ -2698,7 +2698,7 @@ def test_filter_not_iterable(self):
 
     def test_filter_not_list_of_iterable(self):
         if self.sg_version < (7, 0, 0):
-            warnings.warn("Test bypassed because SG server used does not support this feature.", FutureWarning)
+            warnings.warn("Test bypassed because PTR server used does not support this feature.", FutureWarning)
             return
 
         filters = [
@@ -2716,7 +2716,7 @@ def test_filter_not_list_of_iterable(self):
 
     def test_multiple_latest_filters(self):
         if self.sg_version < (7, 0, 0):
-            warnings.warn("Test bypassed because SG server used does not support this feature.", FutureWarning)
+            warnings.warn("Test bypassed because PTR server used does not support this feature.", FutureWarning)
             return
 
         filters = [
@@ -2740,7 +2740,7 @@ def test_modify_visibility(self):
         # If the version of Shotgun is too old, do not run this test.
         # TODO: Update this with the real version number once the feature is released.
         if self.sg_version < (8, 5, 0):
-            warnings.warn("Test bypassed because SG server used does not support this feature.", FutureWarning)
+            warnings.warn("Test bypassed because PTR server used does not support this feature.", FutureWarning)
             return
 
         field_display_name = "Project Visibility Test"
diff --git a/tests/test_client.py b/tests/test_client.py
index f7e783b2c..9a6b0f9b8 100644
--- a/tests/test_client.py
+++ b/tests/test_client.py
@@ -244,7 +244,7 @@ def test_authorization(self):
         self.assertEqual(expected, headers.get("Authorization"))
 
     def test_localization_header_default(self):
-        """Localization header not passed to server without explicitly setting SG localization config to True"""
+        """Localization header not passed to server without explicitly setting PTR localization config to True"""
         self.sg.info()
 
         args, _ = self.sg._http_request.call_args
@@ -254,7 +254,7 @@ def test_localization_header_default(self):
         self.assertEqual(None, headers.get("locale"))
 
     def test_localization_header_when_localized(self):
-        """Localization header passed to server when setting SG localization config to True"""
+        """Localization header passed to server when setting PTR localization config to True"""
         self.sg.config.localized = True
 
         self.sg.info()
diff --git a/tests/test_unit.py b/tests/test_unit.py
index c8ce4fcc9..84bd35b60 100644
--- a/tests/test_unit.py
+++ b/tests/test_unit.py
@@ -440,7 +440,7 @@ def _check_url_with_urllib(self, url):
         """
         Given a url it will perform a simple request and return a result.
         """
-        # create a request using the opener generated by the SG API.
+        # create a request using the opener generated by the PTR API.
         # The `_build_opener` method internally should use the correct certs.
         opener = self.sg._build_opener(urllib.request.HTTPHandler)
         request = urllib.request.Request(url)
@@ -460,7 +460,7 @@ def test_found_correct_cert(self):
             # Call dirname to remove from __init__.py
             os.path.join(os.path.dirname(api.__file__), "lib", "certifi", "cacert.pem")
         )
-        # Now ensure that the path the SG API has found is correct.
+        # Now ensure that the path the PTR API has found is correct.
         self.assertEqual(cert_path, self.certs)
         self.assertTrue(os.path.isfile(self.certs))
 
