chore: tweak note case study

Author: tianzhou

content/blog/note-case-study.md

@@ -39,19 +39,19 @@ After extensive research, note’s SRE team selected Bytebase to replace their i
 
 ![sso-bb](/content/blog/note-case-study/sso-bb.webp)
 
-Bytebase provides various capabilities to enable more secure and efficient database access, including a unified web-based SQL Editor with fine-grained sensitive data masking and role-based access control. 
+Bytebase provides various capabilities to enable more secure and efficient database access, including a unified web-based SQL Editor with fine-grained sensitive data masking and role-based access control.
 
 ![jit](/content/blog/note-case-study/jit.webp)
 
 ### Web-based SQL Editor
 
-Bytebase offers a web-based SQL Editor that consolidates all permissions management and data access operations into a single tool. This eliminates the need for the in-house tool, SSH proxy server, and local database clients, allowing developers to submit permission requests and access the database in one place, greatly improving convenience.
+Bytebase offers a [web-based SQL Editor](/docs/sql-editor/overview/) that consolidates all permissions management and data access operations into a single tool. This eliminates the need for the in-house tool, SSH proxy server, and local database clients, allowing developers to submit permission requests and access the database in one place, greatly improving convenience.
 
 ![sql-editor](/content/blog/note-case-study/sql-editor.webp)
 
 ### Dynamic Data Masking
 
-Bytebase offers column-level dynamic data masking for our Aurora MySQL databases. When granting access permissions to developers for specific tables, sensitive columns can be dynamically masked based on the user's identity during data queries.
+Bytebase offers column-level [dynamic data masking](/docs/security/data-masking/overview/) for our Aurora MySQL databases. When granting access permissions to developers for specific tables, sensitive columns can be dynamically masked based on the user's identity during data queries.
 
 ![ddm](/content/blog/note-case-study/ddm.webp)
 
@@ -88,13 +88,13 @@ Access request notifications will be pushed to Slack.
 After implementing Bytebase's database access control, the following issues have become apparent. In response, note is considering further leveraging Bytebase's capabilities to address these challenges:
 
 - [External approval via Slack](/docs/api/external-approval/)
- 
+
   Currently, workflow approvals are only carried out on Bytebase. By utilizing the external approval feature, approvals can be processed through Slack.
 
 - [CI/CD for DML and DDL changes](/docs/change-database/change-workflow/)
 
   At present, only read queries are utilized; the aim is to enable modifications for both DML and DDL directly on Bytebase.
 
 - [GitOps workflow with GitHub](/docs/vcs-integration/overview/)
-  
-  Given that SQL is currently managed through GitHub Issues in the existing business process, the introduction of GitOps is expected to enhance operational efficiency.
+
+  Given that SQL is currently managed through GitHub Issues in the existing business process, the introduction of GitOps is expected to enhance operational efficiency.