From b03d51db31cae96322c8509ea9a7ca58b9425103 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E4=BA=BA=E5=AE=B6=E6=95=85=E9=87=8C?= <46512207+raingnight@users.noreply.github.com> Date: Thu, 24 Sep 2026 17:30:44 +0800 Subject: [PATCH] fix(docs): correct documentation typos --- docs/content/docs/data-security-migration.mdx | 2 +- docs/content/docs/field-lineage.cn.mdx | 2 +- docs/content/docs/plugin-development.cn.mdx | 2 +- docs/content/docs/schema-diff.cn.mdx | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/content/docs/data-security-migration.mdx b/docs/content/docs/data-security-migration.mdx index ad1cd92736..0f2fbbf4c9 100644 --- a/docs/content/docs/data-security-migration.mdx +++ b/docs/content/docs/data-security-migration.mdx @@ -124,7 +124,7 @@ DBX has two separate key boundaries: | Local Secret Store key | Encrypts secrets in the local `dbx.db` | Platform credential store, managed data-dir key, or explicit environment key | No | | Sync passphrase | Encrypts the sensitive part of an export/import package | Entered by the user for that package | Only as the package protection, never as the local key | -The managed data-directory key is created only when migration or a sensitive write needs it. Back up it with `dbx.db`. A key stored in the same volume protects the database contents at rest, but it does not protect a stolen copy of the entire volume. +The managed data-directory key is created only when migration or a sensitive write needs it. Back it up with `dbx.db`. A key stored in the same volume protects the database contents at rest, but it does not protect a stolen copy of the entire volume. If the database already contains encrypted values, using a new key makes them unreadable. Restore the original key instead of creating another one. diff --git a/docs/content/docs/field-lineage.cn.mdx b/docs/content/docs/field-lineage.cn.mdx index b2aa9e373e..4908bbb3a5 100644 --- a/docs/content/docs/field-lineage.cn.mdx +++ b/docs/content/docs/field-lineage.cn.mdx @@ -52,7 +52,7 @@ DBX 会把已执行查询作为辅助证据，例如： - `SELECT *`、复杂子查询或厂商扩展语法 - 数据库没有返回完整视图源码 -点击视图结果后，可以结合 [对象浏览器](/cn/docs/object-browser) 中的源码查看人工确认。 +点击视图结果后，可以结合 [对象浏览器](/cn/docs/object-browser) 中的源码进行人工确认。 ## 使用方式 diff --git a/docs/content/docs/plugin-development.cn.mdx b/docs/content/docs/plugin-development.cn.mdx index 27485e57cc..b749e02add 100644 --- a/docs/content/docs/plugin-development.cn.mdx +++ b/docs/content/docs/plugin-development.cn.mdx @@ -49,7 +49,7 @@ my-plugin/ ## Manifest 完整说明 -`manifest.json` 是运行时契约，文件名必须位于插件包根目录。Manifest v1 不接受未声明字段，建议在编辑器中引用仓库内的 [`plugins/manifest.schema.json`](https://github.com/t8y2/dbx/blob/main/plugins/manifest.schema.json)。最小的纯前端 Manifest 如下： +`manifest.json` 是运行时契约，文件必须位于插件包根目录。Manifest v1 不接受未声明字段，建议在编辑器中引用仓库内的 [`plugins/manifest.schema.json`](https://github.com/t8y2/dbx/blob/main/plugins/manifest.schema.json)。最小的纯前端 Manifest 如下： ```json { diff --git a/docs/content/docs/schema-diff.cn.mdx b/docs/content/docs/schema-diff.cn.mdx index 36bbcc07ae..b90387189c 100644 --- a/docs/content/docs/schema-diff.cn.mdx +++ b/docs/content/docs/schema-diff.cn.mdx @@ -124,7 +124,7 @@ DBX 会尽量保留数据库专属语义，而不是把所有 DDL 转成通用 - PostgreSQL / openGauss 等的 Schema、序列、Owner、Rule 和索引特性 - MySQL 兼容数据库的字符集、排序规则、自增和索引语法 - Oracle、达梦、GaussDB、KingbaseES 等的类型和对象限定方式 -- Doris / StarRocks、ClickHouse、Elasticsearch/Easysearch 等只在可可靠处理的结构范围内参与 +- Doris / StarRocks、ClickHouse、Elasticsearch/Easysearch 等只在可靠处理的结构范围内参与 支持连接不代表所有对象都可对比或部署。查看 [数据库支持](/cn/docs/databases) 和结果中的 capability 提示。