SG-34674 Change all the shotgrid/shotgun occurrences in the repository (

#157)

Co-authored-by: Julien Langlois <julien.langlois@autodesk.com>

README.md

@@ -1,10 +1,10 @@
 [![Build Status](https://dev.azure.com/shotgun-ecosystem/Toolkit/_apis/build/status/Configs/tk-config-default2?branchName=master)](https://dev.azure.com/shotgun-ecosystem/Toolkit/_build/latest?definitionId=49&branchName=master)
 
 -------------------------------------------------------------------------
-The ShotGrid Pipeline Toolkit Default Configuration
+The Flow Production Tracking Toolkit Default Configuration
 -------------------------------------------------------------------------
 
-Welcome to the ShotGrid Pipeline Toolkit default configuration!
+Welcome to the Flow Production Tracking Toolkit default configuration!
 
 For more information, go to the following url:
 https://developer.shotgridsoftware.com/8085533c/?title=ShotGrid+Integrations+Admin+Guide

SECURITY.md

@@ -4,19 +4,19 @@
 
 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
-models are more important than ever.
+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
-and performance, we are also backed by Autodesk’s security team, also invests
-heavily in the security for broad range of industries and customers.
+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
-repository, please report it to us as described below.
+If you believe you have found a security vulnerability in any
+Flow Production Tracking-owned repository, please report it to us as described below.
 
 
 ## Reporting Security Issues
@@ -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).
+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).

core/hooks/README

@@ -1,6 +1,6 @@
 This location is for core hook override files.
 
-The ShotGrid Pipeline Toolkit comes with a series of Core Hooks, essentially snippets of python
+The Flow Production Tracking Toolkit comes with a series of Core Hooks, essentially snippets of python
 that contain key operations such as copying a file, creating directories etc.
 
 These hooks are part of the platform distribution and are therefore bundled with the code itself.

env/README.md

@@ -17,8 +17,8 @@ returned by the `pick_environment` hook. These files are:
     building menus in the SG web interface.
 * `asset_step.yml` - Asset context with a pipeline step. This is the environment
     typically associated with an artist's Asset work area.
-* `project.yml` - A ShotGrid project context. Often used when launching a
-    DCC from SG Desktop, providing apps for further refining the context.
+* `project.yml` - A Flow Production Tracking project context. Often used when
+   launching a DCC from SG Desktop, providing apps for further refining the context.
 * `publishedfile_version.yml` - A context for providing functionality when
     viewing PublishedFile or Version entities, typically in SG web interface.
 * `sequence.yml` - A context used for sequence-based workflows.

env/includes/settings/tk-flame.yml

@@ -30,8 +30,8 @@ settings.tk-flame.project:
     tk-multi-loader2: "@settings.tk-multi-loader2.flame"
   location: "@engines.tk-flame.location"
   context_menu: [
-    { name : "Load...", app_instance: "tk-multi-loader2", display_name: "ShotGrid Loader..."},
-    { name : "Shotgun Panel...", app_instance: "tk-multi-shotgunpanel", display_name: "ShotGrid Panel..."}
+    { name : "Load...", app_instance: "tk-multi-loader2", display_name: "Flow Production Tracking Loader..."},
+    { name : "Shotgun Panel...", app_instance: "tk-multi-shotgunpanel", display_name: "Flow Production Tracking Panel..."}
   ]
 
 # shot
@@ -44,6 +44,6 @@ settings.tk-flame.shot:
     tk-multi-loader2: "@settings.tk-multi-loader2.flame"
   location: "@engines.tk-flame.location"
   context_menu: [
-    { name : "Load...", app_instance: "tk-multi-loader2", display_name: "ShotGrid Loader..."},
-    { name : "Shotgun Panel...", app_instance: "tk-multi-shotgunpanel", display_name: "ShotGrid Panel..."}
+    { name : "Load...", app_instance: "tk-multi-loader2", display_name: "Flow Production Tracking Loader..."},
+    { name : "Shotgun Panel...", app_instance: "tk-multi-shotgunpanel", display_name: "Flow Production Tracking Panel..."}
   ]