diff --git a/doc/api/merge_request_approvals.md b/doc/api/merge_request_approvals.md
index 242f1dac485bfbda7039335b7a8c77d537409cba..5aca02f2984d16f5c9059b5f6e011d5f9322eb87 100644
--- a/doc/api/merge_request_approvals.md
+++ b/doc/api/merge_request_approvals.md
@@ -181,7 +181,7 @@ Supported attributes:
 | `approvals_required` | string            | No       | The number of required approvals for this rule. |
 | `group_ids`          | integer           | No       | The IDs of users as approvers. |
 | `name`               | string            | No       | The name of the approval rule. |
-| `rule_type`          | array             | No       | The type of rule. `any_approver` is a pre-configured default rule with `approvals_required` at `0`. Other rules are `regular` (used for regular [merge request approval rules](../../ee/user/project/merge_requests/approvals/rules.md)) and `report_approver`. `report_approver` is used automatically when an approval rule is created from configured and enabled [merge request approval policies](../../ee/user/application_security/policies/scan-result-policies.md) and should not be used to create approval rule with this API. |
+| `rule_type`          | array             | No       | The type of rule. `any_approver` is a pre-configured default rule with `approvals_required` at `0`. Other rules are `regular` (used for regular [merge request approval rules](../user/project/merge_requests/approvals/rules.md)) and `report_approver`. `report_approver` is used automatically when an approval rule is created from configured and enabled [merge request approval policies](../user/application_security/policies/scan-result-policies.md) and should not be used to create approval rule with this API. |
 | `user_ids`           | array             | No       | The IDs of groups as approvers. |
 
 Example request:
@@ -530,7 +530,7 @@ Supported attributes:
 | `group_ids`                         | Array             | No       | The IDs of groups as approvers. |
 | `protected_branch_ids`              | Array             | No       | The IDs of protected branches to scope the rule by. To identify the ID, [use the API](protected_branches.md#list-protected-branches). |
 | `report_type`                       | string            | No       | The report type required when the rule type is `report_approver`. The supported report types are `license_scanning` [(Deprecated in GitLab 15.9)](../update/deprecations.md#license-check-and-the-policies-tab-on-the-license-compliance-page) and `code_coverage`. |
-| `rule_type`                         | string            | No       | The type of rule. `any_approver` is a pre-configured default rule with `approvals_required` at `0`. Other rules are `regular` (used for regular [merge request approval rules](../../ee/user/project/merge_requests/approvals/rules.md)) and `report_approver`. `report_approver` is used automatically when an approval rule is created from configured and enabled [merge request approval policies](../../ee/user/application_security/policies/scan-result-policies.md) and should not be used to create approval rule with this API. |
+| `rule_type`                         | string            | No       | The type of rule. `any_approver` is a pre-configured default rule with `approvals_required` at `0`. Other rules are `regular` (used for regular [merge request approval rules](../user/project/merge_requests/approvals/rules.md)) and `report_approver`. `report_approver` is used automatically when an approval rule is created from configured and enabled [merge request approval policies](../user/application_security/policies/scan-result-policies.md) and should not be used to create approval rule with this API. |
 | `user_ids`                          | Array             | No       | The IDs of users as approvers. If you provide both `user_ids` and `usernames`, both lists of users are added. |
 | `usernames`                         | string array      | No       | The usernames of approvers for this rule (same as `user_ids` but requires a list of usernames). If you provide both `user_ids` and `usernames`, both lists of users are added. |
 
diff --git a/doc/architecture/blueprints/cells/infrastructure/postgresql.md b/doc/architecture/blueprints/cells/infrastructure/postgresql.md
index 78539b219b0c1381e7674ab447247692d93d2b4b..77a6600c86310522a29ae4d96bc08d49cadb7729 100644
--- a/doc/architecture/blueprints/cells/infrastructure/postgresql.md
+++ b/doc/architecture/blueprints/cells/infrastructure/postgresql.md
@@ -174,7 +174,7 @@ Currently, there is no inherent shortcoming of PostgreSQL itself that justifies
 
 Further details below:
 
-- [Alternatives To Postgres DB (Google Spanner vs AlloyDB)]([gitlab-com/gl-infra/production-engineering#24662](https://gitlab.com/gitlab-com/gl-infra/production-engineering/-/issues/24662))
+- [Alternatives To Postgres DB (Google Spanner vs AlloyDB)](https://gitlab.com/gitlab-com/gl-infra/production-engineering/-/issues/24662)
 - [Switching to a proprietary database, instead of PostgreSQL](https://gitlab.com/gitlab-com/gl-infra/production-engineering/-/issues/24673)
 
 ### Cloud SQL