[#33] [PR Feedback] Updated all TDS references to correct product name

helix/devops/development/local-deployment.rst

@@ -27,9 +27,9 @@ frequency of this task it is imperative that this is easy. Tools and
 automated scripts can help this to become almost transparent for the
 developer.
 
-.. admonition:: Sitecore Helix Examples - TDS
+.. admonition:: Sitecore Helix Examples - Sitecore TDS
 
-    The TDS version of Helix Basic Company uses the built-in
+    The Sitecore TDS version of Helix Basic Company uses the built-in
     `capability of TDS <http://hedgehogdevelopment.github.io/tds/chapter4.html>`__
     to deploy files to the web root on build. To avoid the need for a
     TDS project for modules which do not have associated items, a single
@@ -43,7 +43,7 @@ developer.
 
             Figure: File deployment location, originating in the ``TdsGlobal.config``
 
-    You can also enable the *Content File Sync* feature of TDS to automatically
+    You can also enable the *Content File Sync* feature of Sitecore TDS to automatically
     deploy changes to any content files, such as Razor views and CSS/JS files.
 
         .. figure:: _static/tds-content-file-sync.png

helix/devops/integration/integration.rst

@@ -18,8 +18,8 @@ Depending on your tools stack – version control, configuration
 management, item serialization etc. – various tools can help you with
 the integration of your modules and solutions into a distributable
 package. The format of this package will depend on the deployment
-strategy and tools you choose. For example, Team Development for
-Sitecore covers the complete application lifecycle from development
+strategy and tools you choose. For example, Sitecore TDS
+covers the complete application lifecycle from development
 through to integration, and supports generation of Sitecore Update and
 NuGet packages that can be automatically installed with for example
 `Octopus Deploy <https://octopus.com/>`__.

helix/principles/architecture-principles/layers.rst

@@ -75,7 +75,7 @@ to indicate the layer/source of the items contained there:
 .. admonition:: Sitecore Helix Examples
 
     The Helix Examples use the built-in Sitecore layer folders for organizing
-    items, and serialize items from them using either TDS or Unicorn.
+    items, and serialize items from them using either Sitecore TDS or Unicorn.
     (See :doc:`/principles/sitecore-items/development`)
 
     In Visual Studio, the layers are defined as solution folders:
@@ -291,4 +291,4 @@ there is no recommended standard for naming this layer.
 
     Some of the Sitecore Helix Examples use a small *Environment* layer for projects
     which handle deployment to the main Sitecore Website/Platform service, either
-    using Team Development for Sitecore or Helix Publishing Pipeline.
+    using Sitecore TDS or Helix Publishing Pipeline.

helix/principles/sitecore-items/development.rst

@@ -32,8 +32,8 @@ such as:
 
         Figure: Template items in the Helix Basic Company *Feature/Basic Content* module
 
-Versioning items in modules with TDS
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Versioning items in modules with Sitecore TDS
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 Managing the Definition Items along with the business logic that uses
 them poses a technical challenge, as the items are physically stored in
@@ -44,14 +44,14 @@ serialization comes in handy.
 Serialization allows items in the databases (typically in the Master and
 Core database) to be written to disk in a text-based format and
 subsequently restored into a database. Sitecore provides the
-`Team Development for Sitecore (TDS) <https://www.teamdevelopmentforsitecore.com/TDS-Classic>`__
+`Sitecore TDS <https://www.teamdevelopmentforsitecore.com/TDS-Classic>`__
 Visual Studio plugin which allows you to serialize and source control
 Sitecore items within a Visual Studio project.
 
 The Helix conventions define that serialized items should be versioned
 as part of the owning module, next to the code and project files. Place
 the serialized items on disk in a subfolder beneath the module. When using
-TDS, the recommended folder structure is:
+Sitecore TDS, the recommended folder structure is:
 
 ::
 
@@ -74,16 +74,16 @@ TDS, the recommended folder structure is:
 When placing the TDS projects within your Visual Studio solution for a module, always place
 them within the solution folder for the associated module.
 
-TDS includes a number of features to assist when working across multiple
-Helix modules in a Visual Studio Solution. See `TDS documentation <http://hedgehogdevelopment.github.io/tds/>`__
+Sitecore TDS includes a number of features to assist when working across multiple
+Helix modules in a Visual Studio Solution. See `Sitecore TDS documentation <http://hedgehogdevelopment.github.io/tds/>`__
 for information on `Global Configuration <http://hedgehogdevelopment.github.io/tds/chapter4.html#global-config>`__,
 `Multi-Project Properties <http://hedgehogdevelopment.github.io/tds/chapter4.html#multi-project-properties>`__,
 `Sync All Projects <http://hedgehogdevelopment.github.io/tds/chapter4.html#sync-all-projects-using-history-window>`__,
 `Quick Push <http://hedgehogdevelopment.github.io/tds/chapter4.html#quick-push-items>`__, and more.
 
 .. admonition:: Sitecore Helix Examples
 
-    The TDS version of Helix Basic Company uses TDS to manage Sitecore items
+    The TDS version of Helix Basic Company uses Sitecore TDS to manage Sitecore items
     for each module.
 
     .. figure:: _static/basic-company-tds-projects.png

helix/principles/visual-studio/projects.rst

@@ -2,8 +2,8 @@ Projects
 ~~~~~~~~
 
 A Visual Studio solution can host a number of different project types,
-such as Web Application projects, unit test projects, Team Development
-for Sitecore (TDS) projects, behavioural testing projects, Xamarin
+such as Web Application projects, unit test projects, Sitecore
+TDS projects, behavioural testing projects, Xamarin
 projects, etc., but modules are always grouped by their logical
 connection to a module – and never by type.