[doc] release-3.0.6 EN: split Storage section and promote Lakehouse bug-fix groupings#3777
Merged
Merged
Conversation
…ug-fix groupings The zh page for this release is more carefully organised than EN. Cross-port two structural improvements from zh: 1. Improvements section — EN `### Storage` was a catch-all that lumped together three distinct categories (data ingestion, primary key model, storage compaction). Split it into three proper H3s matching zh (`### Data Ingestion`, `### Primary Key Model`, `### Storage`) so each bullet sits under the right topic. Bullet order, content, and PR references are preserved; only their grouping changes. 2. Bug Fixes › Lakehouse — EN used bold paragraph leads (`**Export fixes**`, `**Catalog fixes**`, `**File formats**`) as ad-hoc grouping inside a bullet list. Promote them to proper H4 headings to match zh's `#### Export 修复` / `#### Catalog 修复` / `#### 文件格式` structure. This also flattens the nested 1-level-deep bullets back to the standard top-level list style used elsewhere on the page. No content additions; PR-link set is unchanged (98 unique refs both sides). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
While auditing 3.0.6 zh/EN parity, the zh page turned out to be more carefully organised than EN. Cross-port two structural improvements from zh:
1. Improvements section: split `### Storage`
EN `### Storage` was a catch-all that lumped together three distinct categories of bullets:
Split it into three proper H3s — `### Data Ingestion`, `### Primary Key Model`, `### Storage` — matching zh's `### 导入` / `### 主键模型` / `### 存储优化`. Bullet order, content, and PR refs are preserved; only grouping changes.
2. Bug Fixes › Lakehouse: promote ad-hoc groupings to H4
EN used bold paragraph leads (`Export fixes`, `Catalog fixes`, `File formats`) as ad-hoc sub-groupings inside a bullet list. zh uses proper H4 headings (`#### Export 修复`, `#### Catalog 修复`, `#### 文件格式`). Promote EN to the same H4 structure and flatten the nested 1-level-deep bullets to top-level so the on-page navigation matches.
No content additions; the set of PR references is unchanged on both sides (98 unique refs each).
Test plan