Remove empty include file and its references

Author: Steve Danielson

docs/pipelines/build/variables.md

@@ -13,8 +13,6 @@ monikerRange: '<= azure-devops'
 
 [!INCLUDE [version-lt-eq-azure-devops](../../includes/version-lt-eq-azure-devops.md)]
 
-[!INCLUDE [temp](../includes/concept-rename-note.md)]
-
 Variables give you a convenient way to get key bits of data into various parts of your pipeline.
 This is a list of predefined variables that are available for your use. There may be a few other predefined variables, but they're mostly for internal use.
 

docs/pipelines/create-first-pipeline.md

@@ -339,8 +339,6 @@ From the **More actions** :::image type="icon" source="../media/icons/more-actio
 
 ::: moniker range="<= azure-devops-2020"
 
-[!INCLUDE [temp](includes/concept-rename-note.md)]
-
 ::: moniker-end
 
 ::: moniker range=">= azure-devops-2019 < azure-devops"

docs/pipelines/get-started/pipelines-get-started.md

@@ -21,10 +21,6 @@ The latest way to build pipelines is with the [YAML pipeline editor](yaml-pipeli
 
 ::: moniker-end
 
-
-
-[!INCLUDE [temp](../includes/concept-rename-note.md)]
-
 ## Automate tests, builds, and delivery
 
 Continuous integration (CI) automates tests and builds for your project. CI helps to catch bugs or issues early in the development cycle, when they're easier and faster to fix. Items known as artifacts are produced from CI systems. They're used by the continuous delivery release pipelines to drive automatic deployments.

docs/pipelines/includes/concept-rename-note.md

@@ -13,8 +13,6 @@ monikerRange: '<= azure-devops'
 
 [!INCLUDE [version-lt-eq-azure-devops](../../includes/version-lt-eq-azure-devops.md)]
 
-[!INCLUDE [temp](../includes/concept-rename-note.md)]
-
 You can use an Azure Resource Manager service connection to connect to Azure resources through service principal authentication or through an Azure managed service identity. If you use a Resource Manager service connection, you can use a pipeline to deploy to an Azure resource like an Azure App Service app without authenticating each time.
 
 You have multiple options for connecting to Azure by using Azure Resource Manager service connections:

docs/pipelines/library/connect-to-azure.md

@@ -18,8 +18,6 @@ Variable groups store values and secrets that you might want to be [passed into
 
 Secret variables in Variables groups are [protected resources](../security/resources.md). You can add combinations of approvals, checks, and pipeline permissions to limit access to secret variables in a variable group. Access to non-secret variables is not limited by approvals, checks, and pipeline permissions.
 
-[!INCLUDE [temp](../includes/concept-rename-note.md)]
-
 ## Create a variable group
 
 #### [YAML](#tab/yaml/)

docs/pipelines/library/variable-groups.md

@@ -13,8 +13,6 @@ monikerRange: '<= azure-devops'
 
 [!INCLUDE [version-lt-eq-azure-devops](../../includes/version-lt-eq-azure-devops.md)]
 
-[!INCLUDE [temp](../includes/concept-rename-note.md)]
-
 ::: moniker range="azure-devops"
 Pipeline permissions and roles help you securely manage your pipelines. You can set hierarchical permissions at the organization, project, and object levels for all pipelines in a project or for an individual pipeline. You can update pipeline permissions with security groups or by [adding individual users](set-permissions.md).
 ::: moniker-end

docs/pipelines/policies/permissions.md

@@ -11,8 +11,6 @@ monikerRange: "<=azure-devops"
 
 [!INCLUDE [version-lt-eq-azure-devops](../../includes/version-lt-eq-azure-devops.md)]
 
-[!INCLUDE [temp](../includes/concept-rename-note.md)]
-
 You can customize how your pipeline runs are numbered. The default value for run number is `$(Date:yyyyMMdd).$(Rev:r)`. 
 
 In Azure DevOps `$(Rev:r)` is a special variable format that only works in the build number field. When a build is completed, if nothing else in the build number has changed, the `Rev` integer value increases by one.

docs/pipelines/process/run-number.md

@@ -11,8 +11,6 @@ monikerRange: '<= azure-devops'
 
 [!INCLUDE [version-lt-eq-azure-devops](../../includes/version-lt-eq-azure-devops.md)]
 
-[!INCLUDE [temp](../includes/concept-rename-note.md)]
-
 A **task** performs an action in a pipeline and is a packaged script or procedure that's
 abstracted with a set of inputs. Tasks are the building blocks for defining automation in a pipeline. 
 

docs/pipelines/process/tasks.md

@@ -14,8 +14,6 @@ monikerRange: '<= azure-devops'
 
 [!INCLUDE [version-lt-eq-azure-devops](../../includes/version-lt-eq-azure-devops.md)]
 
-[!INCLUDE [temp](../includes/concept-rename-note.md)]
-
 Variables give you a convenient way to get key bits of data into various parts of the pipeline. The most common use of variables is to define a value that you can then use in your pipeline. All variables are strings and are mutable. The value of a variable can change from run to run or job to job of your pipeline.
 
 When you define the same variable in multiple places with the same name, the most locally scoped variable wins. So, a variable defined at the job level can override a variable set at the stage level. A variable defined at the stage level overrides a variable set at the pipeline root level. A variable set in the pipeline root level overrides a variable set in the Pipeline settings UI. 

docs/pipelines/process/variables.md

@@ -11,8 +11,6 @@ monikerRange: '<= azure-devops'
 
 [!INCLUDE [version-lt-eq-azure-devops](../../includes/version-lt-eq-azure-devops.md)]
 
-[!INCLUDE [temp](../includes/concept-rename-note.md)]
-
 You can automatically deploy your database updates to Azure SQL database after every successful build.
 
 ## DACPAC