Improve the annotations of DORA Deployment frequency and Lead time fo…

…r changes (#772) * docs: update deploy frequency annotation * docs: update clt annotation --------- Co-authored-by: Startrekzky <[email protected]>
apache · Jul 25, 2024 · bd8c422 · bd8c422
1 parent b6f4935
commit bd8c422
Show file tree

Hide file tree

Showing 6 changed files with 2 additions and 2 deletions.
diff --git a/docs/Configuration/images/deployment_definition.png b/docs/Configuration/images/deployment_definition.png
diff --git a/docs/Configuration/images/lead_time_for_changes_definition.png b/docs/Configuration/images/lead_time_for_changes_definition.png
diff --git a/docs/Metrics/LeadTimeForChanges.md b/docs/Metrics/LeadTimeForChanges.md
@@ -26,7 +26,7 @@ This metric is quite similar to [PR Cycle Time](PRCycleTime.md). The difference
 
 ![](../Configuration/images/lead_time_for_changes_definition.png)
 
-PR cycle time is pre-calculated by the `dora` plugin during every data collection. You can find it in `pr_cycle_time` in [table.project_pr_metrics](https://devlake.apache.org/docs/DataModels/DevLakeDomainLayerSchema/#project_pr_metrics) of DevLake's database.
+[PR cycle time](../Metrics/PRCycleTime.md) is pre-calculated by the `dora` plugin during every data collection. You can find it in `pr_cycle_time` in [table.project_pr_metrics](https://devlake.apache.org/docs/DataModels/DevLakeDomainLayerSchema/#project_pr_metrics) of DevLake's database.
 
 Below are the 2023 DORA benchmarks for different development teams from Google's report. However, it's difficult to tell which group a team falls into when the team's median lead time for changes is `between one week and one month`. Therefore, DevLake provides its own benchmarks to address this problem:
 

diff --git a/versioned_docs/version-v1.0/Configuration/images/deployment_definition.png b/versioned_docs/version-v1.0/Configuration/images/deployment_definition.png
diff --git a/...ned_docs/version-v1.0/Configuration/images/lead_time_for_changes_definition.png b/...ned_docs/version-v1.0/Configuration/images/lead_time_for_changes_definition.png
diff --git a/versioned_docs/version-v1.0/Metrics/LeadTimeForChanges.md b/versioned_docs/version-v1.0/Metrics/LeadTimeForChanges.md
@@ -26,7 +26,7 @@ This metric is quite similar to [PR Cycle Time](PRCycleTime.md). The difference
 
 ![](../Configuration/images/lead_time_for_changes_definition.png)
 
-PR cycle time is pre-calculated by the `dora` plugin during every data collection. You can find it in `pr_cycle_time` in [table.project_pr_metrics](https://devlake.apache.org/docs/DataModels/DevLakeDomainLayerSchema/#project_pr_metrics) of DevLake's database.
+[PR cycle time](../Metrics/PRCycleTime.md) is pre-calculated by the `dora` plugin during every data collection. You can find it in `pr_cycle_time` in [table.project_pr_metrics](https://devlake.apache.org/docs/DataModels/DevLakeDomainLayerSchema/#project_pr_metrics) of DevLake's database.
 
 Below are the 2023 DORA benchmarks for different development teams from Google's report. However, it's difficult to tell which group a team falls into when the team's median lead time for changes is `between one week and one month`. Therefore, DevLake provides its own benchmarks to address this problem: