SDCD-1030: adding service catalog link naming parameters to the dora and cd visibility docs

content/en/continuous_delivery/features/code_changes_detection.md

@@ -112,7 +112,7 @@ To correctly understand the code changes that a deployment has introduced, only
 
 This can be done in [Software Catalog][5] by specifying, for the interested services, the source code glob file path patterns in the [service definition][4].
 
-If the service definition contains a **full** GitHub or GitLab URL to the application folder, a single path pattern is automatically used.
+If the service definition contains a **full** GitHub or GitLab URL to the application folder, a single path pattern is automatically used. The link type must be **repo** and the link name must be either "Source" or the name of the service (`shopist` in the examples below).
 
 **Example (schema version v2.2):**
 

content/en/dora_metrics/setup/deployments.md

@@ -232,7 +232,7 @@ If the source code of multiple services is present in the same repository, furth
 
 To filter the commits measured to only the ones that affect the service, specify the source code glob file path patterns in the [service definition][5].
 
-If the service definition contains a **full** GitHub or GitLab URL to the application folder, a single path pattern is automatically used.
+If the service definition contains a **full** GitHub or GitLab URL to the application folder, a single path pattern is automatically used. The link type must be **repo** and the link name must be either "Source" or the name of the service (`shopist` in the examples below).
 
 **Example (schema version v2.2):**
 {{< tabs >}}