addressed Deepak's feedback

Author: silviuandrica

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

@@ -5,7 +5,7 @@ author: silviuandrica
 ms.date: 02/04/2022
 ---
 
-An informational run tells you Azure DevOps failed to retrieve a YAML pipeline's source code. Source code retrieval happens in response to external events, for example, a pushed commit. It also happens in response to internal triggers, for example, to check if there are code changes and start a scheduled run or not. Thus, the existence of such a run doesn't always mean Azure DevOps was going to run the pipeline. 
+An informational run tells you Azure DevOps failed to retrieve a YAML pipeline's source code. Source code retrieval happens in response to external events, for example, a pushed commit. It also happens in response to internal triggers, for example, to check if there are code changes and start a scheduled run or not. Source code retrieval can fail for multiple reasons, with a frequent one being request throttling by the git repository provider. The existence of an informational run doesn't necessarily mean Azure DevOps was going to run the pipeline. 
 
 An informational run looks like in the following screenshot. 
 

docs/pipelines/process/information-run.md

@@ -36,6 +36,8 @@ A pipeline may run in response to:
 
 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.
 
+Request throttling by the git repository provider is a frequent cause of Azure DevOps Services creating an informational run. Throttling occurs when Azure DevOps makes too many requests to the repository in a short amount of time. This can be due to a spike in commit activity, for example. Throttling issues are generally transitory.
+
 ## Next Steps
 
 Learn more about [Triggers](../build/triggers.md) and building your [GitHub](../repos/github.md) or [BitBucket](../repos/bitbucket.md) repositories.

docs/pipelines/repos/bitbucket.md

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

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.
 
-## Informational pipeline runs
+## Informational runs
 [!INCLUDE [informational-runs](../includes/information-run-include.md)]
 
-Learn more about [informational pipeline runs](../process/information-run.md).
+Learn more about [informational runs](../process/information-run.md).
 
 ## FAQ
 
@@ -95,7 +95,7 @@ Follow each of these steps to troubleshoot your failing triggers:
 
 #### I did not push any updates to my code, however the pipeline is still being triggered.
 
-* The continuous integration trigger for Bitbucket works through polling. After each polling interval, Azure Pipelines attempts to contact the Bitbucket server to check if there have been any updates to the code. If Azure Pipelines is unable to reach the Bitbucket server (possibly due to a network issue), then we start a new run anyway assuming that there might have been code changes. In a few cases, Azure Pipelines may also create a dummy failed build with an error message to indicate that it was unable to reach the server.
+* The continuous integration trigger for Bitbucket works through polling. After each polling interval, Azure Pipelines attempts to contact the Bitbucket server to check if there have been any updates to the code. If Azure Pipelines is unable to reach the Bitbucket server (possibly due to a network issue), then we start a new run anyway assuming that there might have been code changes. When Azure Pipelines cannot retrieve a YAML pipeline's code, it will create an [informational run](../process/information-run.md).
 
 ### Failing checkout