From 5aed7098bd8838a1d5f34a19a67debb44abe1951 Mon Sep 17 00:00:00 2001 From: Amritpal Nagra Date: Mon, 28 Nov 2022 16:34:51 +0530 Subject: [PATCH] fix misleading wording with hyperlink Signed-off-by: Amritpal Nagra --- docs/tutorials/configuring-plugin-databases.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/tutorials/configuring-plugin-databases.md b/docs/tutorials/configuring-plugin-databases.md index 8cb78bff60..edbe2dd737 100644 --- a/docs/tutorials/configuring-plugin-databases.md +++ b/docs/tutorials/configuring-plugin-databases.md @@ -21,8 +21,8 @@ instance or cluster. With infrastructure defined as code or data (Terraform, AWS CloudFormation, etc.), you may have database credentials which lack permissions to create new databases or you do not have control over the database names. In these -instances, you can set the database name and connection information on a per -plugin basis as mentioned earlier. +instances, you can do [connection configuration per plugin basis] +(#connection-configuration-per-plugin). Backstage supports all of these use cases with the `DatabaseManager` provided by `@backstage/backend-common`. We will now cover how to use and configure