Merged PR 413241: vsts-docs-pr terminology sweep

•	Azure\s*DevOps\s*Project (edited to Azure DevOps Projects when naming the services, made plural)
•	Azure\s*DevOps\s*project (removed “Azure DevOps” where appropriate)
•	Azure\s*DevOps\s*Services\s*project (removed “Azure DevOps Services” where appropriate)
•	Azure\s*DevOps\s*Services\s*account (removed “account” and replaced with organization, if appropriate)
•	Azure\s*DevOps\s*organization (for many instances, I removed “Azure DevOps” where appropriate)
•	Azure\s*DevOps\s*Services\s*organization (removed “Azure DevOps Services” where appropriate)
•	Visual\s*Studio\s*Marketplace (specified the Azure DevOps tab where appropriate)

Related work items: #1402944

Author: Chrystal Comley

docs/_shared/glossary-terms/collections.md

@@ -3,6 +3,6 @@ ms.topic: include
 ---
 
 ## Collections  
-A collection is a container for a number of Azure DevOps projects. A default collection is created when you sign up with Azure DevOps Services or install Team Foundation Server. Within Azure DevOps Services, a collection corresponds to an organization. For on-premises TFS deployments, you can add and manage collections to specify the logical and physical resources available to the projects within the collection. 
+A collection is a container for a number of projects in Azure DevOps. A default collection is created when you sign up with Azure DevOps Services or install Team Foundation Server. Within Azure DevOps Services, a collection corresponds to an organization. For on-premises TFS deployments, you can add and manage collections to specify the logical and physical resources available to the projects within the collection. 
 
 Learn more: [About projects and scaling your organization](/azure/devops/organizations/projects/about-projects), [Manage organizations](/azure/devops/organizations/accounts/organization-management) or [Manage project collections in Team Foundation Server](/tfs/server/admin/manage-team-project-collections).

docs/_shared/glossary-terms/extensions.md

@@ -4,4 +4,4 @@ ms.topic: include
 
 ## Extensions
 
-Extensions are simple add-ons that are used to customize and extend the DevOps experience of Azure DevOps Services and TFS. They are written with standard technologies—HTML, JavaScript, CSS—and can be developed using your preferred development tools. Hundreds of extensions are available from the [Visual Studio Marketplace](https://marketplace.visualstudio.com/).
+Extensions are simple add-ons that are used to customize and extend the DevOps experience of Azure DevOps Services and TFS. They are written with standard technologies—HTML, JavaScript, CSS—and can be developed using your preferred development tools. Hundreds of extensions are available from the [Visual Studio Marketplace](https://marketplace.visualstudio.com/), Azure DevOps tab.

docs/_shared/glossary-terms/organizations.md

@@ -4,6 +4,6 @@ ms.topic: include
 
 ## Organizations
 
-An Azure DevOps organization corresponds to a business unit you define to support a set of services and users. It can be for your whole company, a specific business unit within your company, or just you. Each organization is associated with a separate URL, such as `https://dev.azure.com/fabrikam-engineering`, and is mostly isolated from other organizations.
+An organization in Azure DevOps corresponds to a business unit you define to support a set of services and users. It can be for your whole company, a specific business unit within your company, or just you. Each organization is associated with a separate URL, such as `https://dev.azure.com/fabrikam-engineering`, and is mostly isolated from other organizations.
 
-Learn more: [Define your Azure DevOps organizations and projects](/azure/devops/user-guide/define-organizations-and-projects).
+Learn more: [Define your organizations and projects in Azure DevOps](/azure/devops/user-guide/define-organizations-and-projects).

docs/_shared/qa-azure-why-no-vsts-organization.md

@@ -1,6 +1,6 @@
-#### Q:  Why don't I see my Azure DevOps organization in the Azure portal?
+#### Q:  Why don't I see my organization in the Azure portal?
 
 A:  In both Azure portals, you must have
 [Azure Service Administrator or Co-administrator](/azure/billing-add-change-azure-subscription-administrator) 
-permissions for the Azure subscription that's linked to your organization.
+permissions for the Azure subscription that's linked to your organization in Azure DevOps.
 Also, in the [Azure portal](https://portal.azure.com), you must have project collection administrator or organization owner permissions.

docs/_shared/qa-no-access-existing-features.md

@@ -6,7 +6,7 @@ A: Make sure that users have the correct [access level](https://visualstudio.mic
 
 * Learn [how to change access levels for Team Foundation Server](/azure/devops/organizations/security/change-access-levels).
 
-Some features are available only as [extensions](https://visualstudio.microsoft.com/team-services/compare-features/). You need to install these extensions. Most extensions require you to have at least Basic access, not Stakeholder access. Check the extension's description in the [Visual Studio Marketplace](https://marketplace.visualstudio.com).
+Some features are available only as [extensions](https://visualstudio.microsoft.com/team-services/compare-features/). You need to install these extensions. Most extensions require you to have at least Basic access, not Stakeholder access. Check the extension's description in the [Visual Studio Marketplace](https://marketplace.visualstudio.com), Azure DevOps tab.
 
 For example, to search your code, you can install the free [Code Search extension](https://marketplace.visualstudio.com/items?itemName=ms.vss-code-search), but you need at least Basic access to use the extension.
 

docs/_shared/qa-no-access-extension-features.md

@@ -11,7 +11,7 @@ To help your team improve app quality, you can install the free
 but you'll get different capabilities based on your access level 
 and whether you work offline or connected to Azure DevOps Services or TFS. 
 For more details, see the extension's description 
-in the [Visual Studio Marketplace](https://marketplace.visualstudio.com).
+in the [Visual Studio Marketplace](https://marketplace.visualstudio.com), Azure DevOps tab.
 
 <a name="trial-expired"></a>
 *	If you're using an organization, and you started a free extension trial, 

docs/articles/credential-storage.md

@@ -7,7 +7,7 @@ ms.technology: devops-whitepapers
 ms.author: chcomley
 author: chcomley
 ms.manager: douge
-ms.date: 11/05/2018
+ms.date: 12/04/2018
 monikerRange: 'vsts'
 ---
 
@@ -17,7 +17,7 @@ monikerRange: 'vsts'
 
 ## Credential security
 
-Microsoft is committed to ensuring that your Azure DevOps projects remain safe and secure, without exception. In Azure DevOps, your projects benefit from multiple layers of security and governance technologies, operational practices, and compliance policies. We enforce data privacy and integrity both at rest and in transit. In addition, we adhere to the following practices with respect to the credentials or secrets that Azure DevOps stores.
+Microsoft is committed to ensuring that your projects remain safe and secure, without exception. In Azure DevOps, your projects benefit from multiple layers of security and governance technologies, operational practices, and compliance policies. We enforce data privacy and integrity both at rest and in transit. In addition, we adhere to the following practices with respect to the credentials or secrets that Azure DevOps stores.
 
 ## Alternate credentials (basic auth)
 

docs/articles/migrate-from-tfs.md

@@ -41,7 +41,7 @@ Here's the general process:
 1.	Identify the most important assets that you need to migrate - typically source code, work items, or both. Other assets in TFS - 
 build pipelines, test plans, and so forth - are harder to manually migrate. 
 2.	Identify a good time to make the transition.
-3.	Prepare your target Azure DevOps organizations. Create the organizations and team projects that you need, provision users, and so on.
+3.	Prepare your target organizations. Create the organizations and team projects that you need, provision users, and so on.
 4.	Migrate your data.
 5.	Consider making the source TFS deployments read-only. 
 

docs/articles/migration-import.md

@@ -112,7 +112,7 @@ TfsMigrator prepare /collection:http://fabrikam:8080/tfs/DefaultCollection /tena
 Upon executing this command, TfsMigrator will run a complete validate to ensure that nothing has changed with your collection since the last full validate. 
 If any new issues are detected, then the import files will not be generated. Shortly after the command has started running, an Azure AD login window will appear. 
 You will need to sign in with an identity that belongs to the tenant domain specified in the command. It's important to make sure that the Azure AD tenant specified 
-is the one you want your future Azure DevOps organization to be backed with. For our Fabrikam example the user would enter something similar to what's shown in the below image.
+is the one you want your future organization to be backed with. For our Fabrikam example the user would enter something similar to what's shown in the below image.
 
 > [!IMPORTANT] 
 > Do NOT use a test Azure AD tenant for a test import and your production Azure AD tenant for the production run. Using a test Azure AD tenant can result in identity import issues when you begin your production run with your organization's production Azure AD tenant.
@@ -138,8 +138,8 @@ Here is the breakdown of the fields and what action needs to be taken:
 |    Source             |    Information detailing location and names of source data files used for import.                          |    None - Review information for subfield actions below.  |
 |    ValidationData     |    Contains information needed to help drive your import experience                                        |    The 'ValidationData' section is generated by TfsMigrator. It contains information needed to help drive your import experience, so it's important that you don't edit the values inside of this section or your import could fail to start.   |
 |    Files              |    Name of the files containing import data.                                                               |    None - Review information for subfield actions below. |
-|    Target             |    Properties describing the new Azure DevOps organization to import into.                                     |    None - Review information for subfield actions below. | 
-|    Name        |    Desired name for the organization that will be created during the import.                                  |    Select a name. This name can be quickly changed later after the import has completed. Note – do **NOT** create an Azure DevOps organization with this name before running the import. The organization will be created as part of the import process.                 |
+|    Target             |    Properties describing the new organization to import into.                                     |    None - Review information for subfield actions below. | 
+|    Name        |    Desired name for the organization that will be created during the import.                                  |    Select a name. This name can be quickly changed later after the import has completed. Note – do **NOT** create an organization with this name before running the import. The organization will be created as part of the import process.                 |
 |    Location    |    SAS Key to the Azure storage account hosting the DACPAC.                    |    None – This will be covered in a later step.                                                                                                                                                                                           |
 |    Dacpac         |    A file that packages up your collection database that is used to bring the data in during import.     |    None - In a later step you'll generate this file using your collection and will upload it to an Azure storage account. It will need to be updated based on the name you use when generating the DACPAC later in this process.    |    
 |    ImportType        |    The type of import that you want to run.      |    None - In a later step you will select the type of import to run. |
@@ -179,7 +179,7 @@ Active identities refer to identities that will be users in Azure DevOps Service
 <a id="historical-identities"></a>
 #### Historical Identities
 These are identities that are mapped as 'historical' in the "Expected Import Status" column in the identity map log file. Also, identities that have no line entry present in the file will also become historical. An example of an identity with no entry would be an employee that no longer works at a company. 
-Historical Identities do **NOT** have access to an Azure DevOps organization after migration, do **NOT** have a licenses, and do **NOT** show up as a user in the organization. All that is persisted is the notion of that identity's name in the organization. This way their history can be searched at a later date. It's recommended that historical identities be used for users that are no longer at the company or won't ever be needing access to the Azure DevOps organization. Identities imported historically **CANNOT** be migrated later to become active identities. 
+Historical Identities do **NOT** have access to an organization after migration, do **NOT** have a licenses, and do **NOT** show up as a user in the organization. All that is persisted is the notion of that identity's name in the organization. This way their history can be searched at a later date. It's recommended that historical identities be used for users that are no longer at the company or won't ever be needing access to the organization. Identities imported historically **CANNOT** be migrated later to become active identities. 
 
 ### Understanding an Identity Map Log
 After opening the identity map log file, you will be presented with something similar to the below example. 
@@ -350,7 +350,7 @@ Use the table below to decide where you should create you SQL Azure VM if you're
 |    Central Canada               |    Central Canada              |
 |    East Asia (Hong Kong)        |    East Asia (Hong Kong)       |
 
-> While Azure DevOps Services is available in multiple regions in the United States, only the Central United States region is accepting new Azure DevOps organizations. Customers will not be able to import their data into other United States Azure regions at this time. 
+> While Azure DevOps Services is available in multiple regions in the United States, only the Central United States region is accepting new organizations. Customers will not be able to import their data into other United States Azure regions at this time. 
 
 > [!NOTE]   
 > DACPAC customers should consult the region table in the [uploading DACPAC and import files section](#uploading-the-dacpac-and-import-files). The above guidelines are for SQL Azure VMs only. 

docs/articles/migration-overview.md

@@ -50,7 +50,7 @@ The following features can be included with your import, but are currently in a
 
 * [Azure Artifacts](https://visualstudio.microsoft.com/team-services/package-management/)
 
-When queueing an import you can elect to include preview features with your import. If you do, data related to these features will be copied into your new Azure DevOps Services organization along with all your other data. Should you choose to not include these features then their data will not be copied.
+When queueing an import you can elect to include preview features with your import. If you do, data related to these features will be copied into your new organization along with all your other data. Should you choose to not include these features then their data will not be copied.
 
 For a list of items not included with an import please see the [migration guide](https://aka.ms/TFSDataImport).