informational run

Author: silviuandrica

docs/pipelines/includes/information-run-include.md

@@ -1,6 +1,6 @@
 ---
-title: Information pipeline runs
-description: What are information pipeline runs
+title: Informational runs
+description: What are informational runs
 ms.topic: reference
 ms.assetid: 96a52d0d-5e01-4b30-818d-1893387522cd
 ms.author: sandrica
@@ -9,11 +9,11 @@ ms.date: 02/04/2022
 monikerRange: 'azure-devops'
 ---
 
-An information pipeline run tells you Azure DevOps tried running a YAML pipeline, but failed to retrieve its source code. Such a run looks like in the following screenshot. 
+An informational run tells you Azure DevOps tried running a YAML pipeline, but failed to retrieve its source code. Such a run looks like in the following screenshot. 
 
-![information pipeline run](../process/media/pipeline-information-run.png)
+![informational run](../process/media/pipeline-information-run.png)
 
-You can recognize an information pipeline run by the following attributes:
+You can recognize an informational run by the following attributes:
 - Status is `Canceled`
 - Duration is `< 1s`
 - Run name contains one of the following texts:

docs/pipelines/process/information-run.md

@@ -1,6 +1,6 @@
 ---
-title: Information pipeline runs
-description: What are information pipeline runs
+title: Informational runs
+description: What are informational runs
 ms.topic: reference
 ms.assetid: 96a52d0d-5e01-4b30-818d-1893387522cd
 ms.author: sandrica
@@ -9,13 +9,13 @@ ms.date: 02/03/2022
 monikerRange: 'azure-devops'
 ---
 
-# Information pipeline runs
+# Informational runs
 
 [!INCLUDE [header](../includes/information-run-include.md)]
 
-## When is an information pipeline run created?
+## When is an informational run created?
 
-The first step of running a YAML pipeline is to retrieve its source code. When this step fails, the system creates an information run. These runs are created only if the pipeline's code is in a GitHub or BitBucket repository.
+The first step of running a YAML pipeline is to retrieve its source code. When this step fails, the system creates an informational run. These runs are created only if the pipeline's code is in a GitHub or BitBucket repository.
 
 Retrieving a pipeline's YAML code can fail due to: 
 - Repository provider experiencing an outage
@@ -34,7 +34,7 @@ A pipeline may run in response to:
 - New resource package versions are available
 - Resource containers changes
 
-Here's an example of when an information pipeline run is created. Suppose you have a repo in your local BitBucket Server and a pipeline that builds the code in that repo. Assume you scheduled your pipeline to run every day, at 03:00. Now, imagine it's 03:00 and your BitBucket Server is experiencing an outage. Azure DevOps reaches out to your local BitBucket Server to fetch the pipeline's YAML code, but it can't, because of the outage. At this moment, the system creates an information pipeline run, similar to the one shown in the previous screenshot.
+Here's an example of when an informational run is created. Suppose you have a repo in your local BitBucket Server and a pipeline that builds the code in that repo. Assume you scheduled your pipeline to run every day, at 03:00. Now, imagine it's 03:00 and your BitBucket Server is experiencing an outage. Azure DevOps reaches out to your local BitBucket Server to fetch the pipeline's YAML code, but it can't, because of the outage. At this moment, the system creates an informational run, similar to the one shown in the previous screenshot.
 
 ## Next Steps
 

docs/pipelines/process/scheduled-triggers.md

@@ -631,7 +631,7 @@ In the second schedule, **Sunday 3:00 AM (UTC) weekly latest version build**, th
 
 * You might have updated the service connection used to connect to the repository. This will cause a new run to be scheduled even if you have not updated your source code.
 
-* Azure Pipelines first checks if there are any updates to your code. If Azure Pipelines is unable to reach your repository or get this information, it will create an [information pipeline run](./information-run.md). It is a dummy build to let you know that Azure Pipelines is unable to reach your repository.
+* Azure Pipelines first checks if there are any updates to your code. If Azure Pipelines is unable to reach your repository or get this information, it will create an [informational run](./information-run.md). It is a dummy build to let you know that Azure Pipelines is unable to reach your repository.
 
 ### I see the planned run in the Scheduled runs panel. However, it does not run at that time. Why?
 

docs/pipelines/repos/bitbucket.md

@@ -211,10 +211,10 @@ For included branches, a build will be triggered on each push to a pull request
 
 ---
 
-## Information pipeline runs
-[!INCLUDE [information-runs](../includes/information-run-include.md)]
+## Informational pipeline runs
+[!INCLUDE [informational-runs](../includes/information-run-include.md)]
 
-Learn more about [information pipeline runs](../process/information-run.md).
+Learn more about [informational pipeline runs](../process/information-run.md).
 
 ## FAQ
 

docs/pipelines/repos/github.md

@@ -512,10 +512,10 @@ The following commands can be issued to Azure Pipelines in comments:
 
 If you have the necessary repository permissions, but pipelines aren't getting triggered by your comments, make sure that your membership is **public** in the repository's organization, or directly add yourself as a repository collaborator. Azure Pipelines cannot see private organization members unless they are direct collaborators or belong to a team that is a direct collaborator. You can change your GitHub organization membership from private to public here (replace `Your-Organization` with your organization name): `https://github.com/orgs/Your-Organization/people`.
 
-## Information pipeline runs
-[!INCLUDE [information-runs](../includes/information-run-include.md)]
+## Informational runs
+[!INCLUDE [informational-runs](../includes/information-run-include.md)]
 
-Learn more about [information pipeline runs](../process/information-run.md).
+Learn more about [informational runs](../process/information-run.md).
 
 
 [!INCLUDE [ci-triggers](includes/source-options.md)]

docs/pipelines/repos/on-premises-bitbucket.md

@@ -69,10 +69,10 @@ To allow traffic from Azure DevOps to reach your Bitbucket Server, add the IP ad
 
 Allow Azure Pipelines to attempt accessing the Git server in the **Other Git** service connection.
 
-## Information pipeline runs
-[!INCLUDE [information-runs](../includes/information-run-include.md)]
+## Informational pipeline runs
+[!INCLUDE [informational-runs](../includes/information-run-include.md)]
 
-Learn more about [information pipeline runs](../process/information-run.md).
+Learn more about [informational pipeline runs](../process/information-run.md).
 
 ## FAQ