chore: fix broken links

Author: tianzhou

content/blog/bytebase-vs-cloudbeaver.md

@@ -120,7 +120,7 @@ On the other hand, the more common way to change the schema is to use **Schema E
   ![bb-access-control-adv](/content/blog/bytebase-vs-cloudbeaver/bb-access-control-adv.webp)
 
   Additionally, admins can set different data access controls for different projects, such as restricted access to production data and open access to development data.
-  ![bb-access-project](/content/blog/bytebase-vs-cloudbeaver/bb-access-project.webp)
+  ![bb-access-environment](/content/blog/bytebase-vs-cloudbeaver/bb-access-control-env.webp)
 
 ### Data Masking
 

content/blog/bytebase-vs-dbeaver.md

@@ -111,8 +111,8 @@ On the other hand, the more common way to change the schema is to use **Schema E
   With **Community plan**, if one's not assigned to a project, one can't see the project at all. With **Enterprise plan**, `Project Owner` can grant access to specific databases or tables instead of all project databases to a specific `SQL Editor User`. `Project Developer` can also request to query or export a database or table with a request issue.
   ![bb-access-control-adv](/content/blog/bytebase-vs-dbeaver/bb-access-control-adv.webp)
 
-  Additionally, `Admin`/`DBA` can set different data access controls for various environments, such as restricted access to production data and open access to development data.
-  ![bb-access-project](/content/blog/bytebase-vs-dbeaver/bb-ac-env.webp)
+  Additionally, admins can set different data access controls for various environments, such as restricted access to production data and open access to development data.
+  ![bb-access-environment](/content/blog/bytebase-vs-dbeaver/bb-access-control-env.webp)
 
 ### Data Masking
 

content/blog/bytebase-vs-metabase.md

@@ -116,8 +116,8 @@ Bytebase is designed for developers, DBAs, and platform teams to manage database
   With **Community plan**, if one's not assigned to a project, one can't see the project at all. With **Enterprise plan**, `Project Owner` can grant access to specific databases or tables instead of all project databases to a specific `SQL Editor User`. `Project Developer` can also request to query or export a database or table with a request issue.
   ![bb-access-control-adv](/content/blog/bytebase-vs-metabase/bb-access-control-adv.webp)
 
-  Additionally, `Admin`/`DBA` can set different data access controls for various environments, such as restricted access to production data and open access to development data.
-  ![bb-access-project](/content/blog/bytebase-vs-metabase/bb-access-project.webp)
+  Additionally, admins can set different data access controls for various environments, such as restricted access to production data and open access to development data.
+  ![bb-access-environment](/content/blog/bytebase-vs-metabase/bb-access-control-env.webp)
 
 ### Data masking
 

content/blog/github-vs-gitlab.md

@@ -48,7 +48,7 @@ across the following key areas.
 | Tech Stack            | RoR + MySQL              | RoR + Go + Postgres                               |                                                                                              |
 | Repository Management | ⭐️⭐️⭐️                | ⭐️⭐️⭐️                                         |                                                                                              |
 | Code Review           | ⭐️⭐️                   | ⭐️                                               | Alternatives: [Graphite](https://graphite.dev/), [Gerrit](https://www.gerritcodereview.com/) |
-| Code Search           | ⭐️⭐️                   | ⭐️                                               | Alternatives: [Sourcegraph](sourcegraph.com)                                                 |
+| Code Search           | ⭐️⭐️                   | ⭐️                                               | Alternatives: [Sourcegraph](https://sourcegraph.com/)                                        |
 | Security              | ⭐️⭐️                   | ⭐️⭐️ ⭐️                                        |                                                                                              |
 | Project Management    | ⭐️                      | ⭐️                                               | Alternatives: [Linear](https://linear.app/), [Jira](https://www.atlassian.com/software/jira) |
 | AI                    | ⭐️⭐️⭐️                | ⭐️                                               |                                                                                              |

content/docs/security/data-masking/access-unmasked-data.md

@@ -4,7 +4,7 @@ title: Masking Exemption
 
 <HintBlock type="info">
 
-Masking precedence: [Masking Exemption](/security/data-masking/access-unmasked-data) > [Global Masking Rule](/security/data-masking/global-masking-rule) > [Column Masking](/security/data-masking/column-masking).
+Masking precedence: [Masking Exemption](/docs/security/data-masking/access-unmasked-data) > [Global Masking Rule](/docs/security/data-masking/global-masking-rule) > [Column Masking](/docs/security/data-masking/column-masking).
 
 </HintBlock>
 

content/docs/security/data-masking/column-masking.md

@@ -4,7 +4,7 @@ title: Column Masking
 
 <HintBlock type="info">
 
-Masking precedence: [Masking Exemption](/security/data-masking/access-unmasked-data) > [Global Masking Rule](/security/data-masking/global-masking-rule) > [Column Masking](/security/data-masking/column-masking).
+Masking precedence: [Masking Exemption](/docs/security/data-masking/access-unmasked-data) > [Global Masking Rule](/docs/security/data-masking/global-masking-rule) > [Column Masking](/docs/security/data-masking/column-masking).
 
 </HintBlock>
 

content/docs/security/data-masking/global-masking-rule.md

@@ -4,7 +4,7 @@ title: Global Masking Rule
 
 <HintBlock type="info">
 
-Masking precedence: [Masking Exemption](/security/data-masking/access-unmasked-data) > [Global Masking Rule](/security/data-masking/global-masking-rule) > [Column Masking](/security/data-masking/column-masking).
+Masking precedence: [Masking Exemption](/docs/security/data-masking/access-unmasked-data) > [Global Masking Rule](/docs/security/data-masking/global-masking-rule) > [Column Masking](/docs/security/data-masking/column-masking).
 
 </HintBlock>
 

content/docs/tutorials/api-sql-review.md

@@ -37,7 +37,6 @@ This tutorial will guide you through configuring SQL review rules using the Byte
 1. Go to [Bytebase API Example repo](https://github.com/bytebase/api-example) and clone it.
 
 1. Navigate to the `sql-review` subfolder and follow the instructions in the `README.md` file of the example code repository to execute the scripts.
-   
 1. Replace `bytebase_url`, `bytebase_account`, and `bytebase_password` in the commands below with your own values, then run them to obtain a `bytebase_token` in your terminal.
 
    ```bash
@@ -98,7 +97,7 @@ We'll apply these SQL review rules to `environments` or `projects`. Project-leve
    ![sql-review-env](/content/docs/tutorials/api-sql-review/sql-review-env.webp)
 
 1. Go to `Sample Project` page, click **Setting** on the left sidebar to see the applied the SQL review rules.
-   ![bb-project-setting](/content/docs/tutorials/api-sql-review/bb-project-setting.webp)
+   ![bb-project-setting](/content/docs/tutorials/api-sql-review/sql-review-project-setting.webp)
 
 1. To detach SQL review policies from environments, use the following commands: