Skip to content

docs: lowercase SpacemiT.com domain in CDN hosts and business email - #140

Merged
junlin-luo-spacemit merged 1 commit into
mainfrom
fix/lowercase-cdn-host-and-email-domain
Sep 30, 2026
Merged

junlin-luo-spacemit merged 1 commit into
mainfrom
fix/lowercase-cdn-host-and-email-domain

Conversation

@junlin-luo-spacemit

Copy link
Copy Markdown
Collaborator

Summary

Lowercases the SpacemiT.com domain wherever it appears as a hostname/domain. DNS hostnames and mail domains are case-insensitive, so the mixed-case forms were sloppy and inconsistent with the rest of the repo; they are now all lowercase.

Changes

1. CDN host — cdn-resource.SpacemiT.com → cdn-resource.spacemit.com

20 files: en|zh/*/root_overview.md (line 7, the "PDF Version / PDF 版本" link).

2. Business email domain — business@SpacemiT.com → business@spacemit.com

24 files: en|zh/*/root_overview.md.

3. Datasheet PDF path — k3_CoM260_ds_{en,zh}.pdf → k3_com260_ds_{en,zh}.pdf

2 files: en|zh/k3_com260/com260_ds.md.

26 files changed, 46 insertions(+), 46 deletions(-).

Deliberately NOT changed

Kept as-is Why
SpacemiT in prose (e.g. "launched by SpacemiT") Correct brand name — spacemit is only for hosts/domains
/Oem/SpacemiT/..., "SpacemiT": {, #OemSpacemiT.* in k3_rv2768/rv2768_redfish.md Redfish API contract — lowercasing would make the docs wrong
CDN path casing such as K3-CoM260_brief_*.pdf Verified against the live CDN: the capitalized path returns 200 while lowercase variants return 404

Verification

  • git grep "SpacemiT\.com" → 0 remaining (case-sensitive).
  • Confirmed no other host casing variants exist; every cdn-resource.* host is now uniformly cdn-resource.spacemit.com.
  • Only the host was lowercased — no CDN file paths were touched, since path casing is significant (verified K3-CoM260_brief_en.pdf = 200 vs K3-com260_brief_en.pdf = 404).
  • No changes to zh/ UTF-8 content — byte-diff confirmed the only difference per line is the domain.

- cdn-resource.SpacemiT.com -> cdn-resource.spacemit.com (20 root_overview.md)
- business@SpacemiT.com -> business@spacemit.com (24 root_overview.md)
- k3_CoM260_ds_{en,zh}.pdf -> k3_com260_ds_{en,zh}.pdf in com260_ds.md

Hosts/domains and CDN PDF paths are case-sensitive on the web host.
Brand prose 'SpacemiT' and Redfish /Oem/SpacemiT/ API paths are left as-is.
@junlin-luo-spacemit
junlin-luo-spacemit merged commit e09aa36 into main Sep 30, 2026
2 checks passed
@junlin-luo-spacemit
junlin-luo-spacemit deleted the fix/lowercase-cdn-host-and-email-domain branch September 30, 2026 02:53
@github-actions

Copy link
Copy Markdown

📝 Doc-Review Agent Report

en/k1_muse_book/root_overview.md

  • Line 51: Product name casing: use 'SpacemiT' not 'spacemit'
  • Line 17: [Warning] Terminology: prefer AI compute unit instead of AI compute
  • Line 17: [Suggestion] Entity K1 ai_compute: prefer 2.0 TOPS (found 2 TOPS)
  • Line 35: [Suggestion] Entity K1 ai_compute: prefer 2.0 TOPS (found 2 TOPS)

en/k1_muse_box/root_overview.md

  • Line 43: Product name casing: use 'SpacemiT' not 'spacemit'
  • Line 12: [Suggestion] Entity K1 ai_compute: prefer 2.0 TOPS (found 2 TOPS)
  • Line 25: [Suggestion] Entity K1 ai_compute: prefer 2.0 TOPS (found 2 TOPS)

en/k1_muse_card/root_overview.md

  • Line 41: Product name casing: use 'SpacemiT' not 'spacemit'
  • Line 10: [Warning] Terminology: prefer AI compute unit instead of AI compute
  • Line 10: [Suggestion] Entity K1 ai_compute: prefer 2.0 TOPS (found 2 TOPS)
  • Line 23: [Suggestion] Entity K1 ai_compute: prefer 2.0 TOPS (found 2 TOPS)

en/k1_muse_paper/root_overview.md

  • Line 62: Product name casing: use 'SpacemiT' not 'spacemit'
  • Line 11: [Warning] Terminology: prefer AI compute unit instead of AI compute
  • Line 36: [Warning] Terminology: prefer AI compute unit instead of AI compute
  • Line 21: [Suggestion] Entity K1 ai_compute: prefer 2.0 TOPS (found 2 TOPS)
  • Line 45: [Suggestion] Entity K1 ai_compute: prefer 2.0 TOPS (found 2 TOPS)

en/k1_muse_pi/root_overview.md

  • Line 43: Product name casing: use 'SpacemiT' not 'spacemit'
  • Line 7: [Suggestion] Entity K1 ai_compute: prefer 2.0 TOPS (found 2 TOPS)
  • Line 10: [Suggestion] Entity K1 ai_compute: prefer 2.0 TOPS (found 2 TOPS)
  • Line 23: [Suggestion] Entity K1 ai_compute: prefer 2.0 TOPS (found 2 TOPS)
  • Line 7: [Suggestion] Entity MUSE Pi ai_compute: prefer 2.0 TOPS (found 2 TOPS)
  • Line 10: [Suggestion] Entity MUSE Pi ai_compute: prefer 2.0 TOPS (found 2 TOPS)
  • Line 23: [Suggestion] Entity MUSE Pi ai_compute: prefer 2.0 TOPS (found 2 TOPS)

en/k1_muse_pi_pro/root_overview.md

  • Line 62: Product name casing: use 'SpacemiT' not 'spacemit'
  • Line 40: [Warning] Terminology: prefer AI compute unit instead of AI power
  • Line 40: [Suggestion] Entity K1 ai_compute: prefer 2.0 TOPS (found 2 TOPS)
  • Line 40: [Suggestion] Entity MUSE Pi ai_compute: prefer 2.0 TOPS (found 2 TOPS)

en/k1_muse_shelf/root_overview.md

  • Line 58: Product name casing: use 'SpacemiT' not 'spacemit'
  • Line 43: [Suggestion] Entity K1 ai_compute: prefer 2.0 TOPS (found 2 TOPS)

en/k1_riscv_labkit/root_overview.md

  • Line 50: Product name casing: use 'SpacemiT' not 'spacemit'
  • Line 31: [Warning] Terminology: prefer AI compute unit instead of AI compute
  • Line 40: [Warning] Terminology: prefer I²C instead of I2C
  • Line 31: [Suggestion] Entity K1 ai_compute: prefer 2.0 TOPS (found 2 TOPS)

en/k3_com260/com260_ds.md

  • Line 732: Placeholder found: 'TBD'
  • Line 38: [Warning] Terminology: prefer I²C instead of I2C
  • Line 185: [Warning] Terminology: prefer I²C instead of I2C
  • Line 189: [Warning] Terminology: prefer I²C instead of I2C
  • Line 190: [Warning] Terminology: prefer I²C instead of I2C
  • Line 191: [Warning] Terminology: prefer I²C instead of I2C
  • Line 192: [Warning] Terminology: prefer I²C instead of I2C
  • Line 345: [Warning] Terminology: prefer I²C instead of I2C
  • Line 347: [Warning] Terminology: prefer I²C instead of I2C
  • Line 348: [Warning] Terminology: prefer I²C instead of I2C
  • Line 351: [Warning] Terminology: prefer I²C instead of I2C
  • Line 352: [Warning] Terminology: prefer I²C instead of I2C
  • Line 353: [Warning] Terminology: prefer I²C instead of I2C
  • Line 354: [Warning] Terminology: prefer I²C instead of I2C
  • Line 355: [Warning] Terminology: prefer I²C instead of I2C
  • Line 356: [Warning] Terminology: prefer I²C instead of I2C
  • Line 359: [Warning] Terminology: prefer I²C instead of I2C
  • Line 363: [Warning] Terminology: prefer I²C instead of I2C
  • Line 364: [Warning] Terminology: prefer I²C instead of I2C
  • Line 365: [Warning] Terminology: prefer I²C instead of I2C
  • Line 366: [Warning] Terminology: prefer I²C instead of I2C
  • Line 390: [Warning] Terminology: prefer I²C instead of I2C
  • Line 391: [Warning] Terminology: prefer I²C instead of I2C
  • Line 392: [Warning] Terminology: prefer I²C instead of I2C
  • Line 393: [Warning] Terminology: prefer I²C instead of I2C
  • Line 394: [Warning] Terminology: prefer I²C instead of I2C
  • Line 395: [Warning] Terminology: prefer I²C instead of I2C
  • Line 396: [Warning] Terminology: prefer I²C instead of I2C
  • Line 397: [Warning] Terminology: prefer I²C instead of I2C
  • Line 400: [Warning] Terminology: prefer I²C instead of I2C
  • Line 401: [Warning] Terminology: prefer I²C instead of I2C
  • Line 403: [Warning] Terminology: prefer I²C instead of I2C
  • Line 404: [Warning] Terminology: prefer I²C instead of I2C
  • Line 408: [Warning] Terminology: prefer I²C instead of I2C
  • Line 409: [Warning] Terminology: prefer I²C instead of I2C
  • Line 410: [Warning] Terminology: prefer I²C instead of I2C
  • Line 411: [Warning] Terminology: prefer I²C instead of I2C
  • Line 412: [Warning] Terminology: prefer I²C instead of I2C
  • Line 413: [Warning] Terminology: prefer I²C instead of I2C
  • Line 414: [Warning] Terminology: prefer I²C instead of I2C
  • Line 415: [Warning] Terminology: prefer I²C instead of I2C
  • Line 417: [Warning] Terminology: prefer I²C instead of I2C
  • Line 418: [Warning] Terminology: prefer I²C instead of I2C
  • Line 480: [Warning] Terminology: prefer I²C instead of I2C
  • Line 482: [Warning] Terminology: prefer I²C instead of I2C
  • Line 483: [Warning] Terminology: prefer I²C instead of I2C
  • Line 486: [Warning] Terminology: prefer I²C instead of I2C
  • Line 487: [Warning] Terminology: prefer I²C instead of I2C
  • Line 488: [Warning] Terminology: prefer I²C instead of I2C
  • Line 489: [Warning] Terminology: prefer I²C instead of I2C
  • Line 500: [Warning] Terminology: prefer I²C instead of I2C
  • Line 526: [Warning] Terminology: prefer I²C instead of I2C
  • Line 527: [Warning] Terminology: prefer I²C instead of I2C
  • Line 528: [Warning] Terminology: prefer I²C instead of I2C
  • Line 529: [Warning] Terminology: prefer I²C instead of I2C
  • Line 530: [Warning] Terminology: prefer I²C instead of I2C
  • Line 531: [Warning] Terminology: prefer I²C instead of I2C
  • Line 532: [Warning] Terminology: prefer I²C instead of I2C
  • Line 535: [Warning] Terminology: prefer I²C instead of I2C
  • Line 536: [Warning] Terminology: prefer I²C instead of I2C
  • Line 538: [Warning] Terminology: prefer I²C instead of I2C
  • Line 539: [Warning] Terminology: prefer I²C instead of I2C
  • Line 543: [Warning] Terminology: prefer I²C instead of I2C
  • Line 544: [Warning] Terminology: prefer I²C instead of I2C
  • Line 546: [Warning] Terminology: prefer I²C instead of I2C
  • Line 547: [Warning] Terminology: prefer I²C instead of I2C
  • Line 548: [Warning] Terminology: prefer I²C instead of I2C
  • Line 549: [Warning] Terminology: prefer I²C instead of I2C
  • Line 610: [Warning] Terminology: prefer I²C instead of I2C
  • Line 613: [Warning] Terminology: prefer I²C instead of I2C
  • Line 618: [Warning] Terminology: prefer I²C instead of I2C
  • Line 619: [Warning] Terminology: prefer I²C instead of I2C
  • Line 620: [Warning] Terminology: prefer I²C instead of I2C
  • Line 621: [Warning] Terminology: prefer I²C instead of I2C
  • Line 624: [Warning] Terminology: prefer I²C instead of I2C
  • Line 628: [Warning] Terminology: prefer I²C instead of I2C
  • Line 629: [Warning] Terminology: prefer I²C instead of I2C
  • Line 631: [Warning] Terminology: prefer I²C instead of I2C
  • Line 655: [Warning] Terminology: prefer I²C instead of I2C
  • Line 656: [Warning] Terminology: prefer I²C instead of I2C
  • Line 657: [Warning] Terminology: prefer I²C instead of I2C
  • Line 675: [Warning] Terminology: prefer I²C instead of I2C
  • Line 677: [Warning] Terminology: prefer I²C instead of I2C
  • Line 680: [Warning] Terminology: prefer I²C instead of I2C
  • Line 682: [Warning] Terminology: prefer I²C instead of I2C
  • Line 683: [Warning] Terminology: prefer I²C instead of I2C

en/k3_com260/root_overview.md

  • Line 72: Product name casing: use 'SpacemiT' not 'spacemit'
  • Line 18: [Warning] Terminology: prefer AI compute unit instead of AI compute
  • Line 66: [Warning] Terminology: prefer I²C instead of I2C

en/k3_pico/root_overview.md

  • Line 85: Product name casing: use 'SpacemiT' not 'spacemit'

en/k3_rv2768/root_overview.md

  • Line 64: Product name casing: use 'SpacemiT' not 'spacemit'
  • Line 15: [Warning] Terminology: prefer AI compute unit instead of AI compute
  • Line 33: [Warning] Terminology: prefer AI compute unit instead of AI compute

en/k3_shelf/root_overview.md

  • Line 114: Product name casing: use 'SpacemiT' not 'spacemit'

zh/k1_muse_book/root_overview.md

  • Line 50: Product name casing: use 'SpacemiT' not 'spacemit'
  • Line 17: [Suggestion] Entity K1 ai_compute: prefer 2.0 TOPS (found 2 TOPS)
  • Line 35: [Suggestion] Entity K1 ai_compute: prefer 2.0 TOPS (found 2 TOPS)
  • Line 51: Use full-width '?' instead of '?'

zh/k1_muse_box/root_overview.md

  • Line 43: Product name casing: use 'SpacemiT' not 'spacemit'
  • Line 25: [Warning] Terminology: prefer AI 算力 instead of AI算力
  • Line 9: [Suggestion] Entity K1 cpu_core_count: prefer 8 核 (found 8核)
  • Line 11: [Suggestion] Entity K1 cpu_core_count: prefer 8 核 (found 八核)
  • Line 12: [Suggestion] Entity K1 ai_compute: prefer 2.0 TOPS (found 2 TOPS)
  • Line 25: [Suggestion] Entity K1 cpu_core_count: prefer 8 核 (found 8核)
  • Line 25: [Suggestion] Entity K1 ai_compute: prefer 2.0 TOPS (found 2 TOPS)
  • Line 44: Use full-width '?' instead of '?'

zh/k1_muse_card/root_overview.md

  • Line 42: Product name casing: use 'SpacemiT' not 'spacemit'
  • Line 23: [Warning] Terminology: prefer AI 算力 instead of AI算力
  • Line 7: [Suggestion] Entity K1 cpu_core_count: prefer 8 核 (found 八核)
  • Line 9: [Suggestion] Entity K1 cpu_core_count: prefer 8 核 (found 八核)
  • Line 10: [Suggestion] Entity K1 ai_compute: prefer 2.0 TOPS (found 2 TOPS)
  • Line 23: [Suggestion] Entity K1 cpu_core_count: prefer 8 核 (found 8核)
  • Line 23: [Suggestion] Entity K1 ai_compute: prefer 2.0 TOPS (found 2 TOPS)

zh/k1_muse_paper/root_overview.md

  • Line 60: Product name casing: use 'SpacemiT' not 'spacemit'
  • Line 19: [Suggestion] Entity K1 ai_compute: prefer 2.0 TOPS (found 2 TOPS)
  • Line 43: [Suggestion] Entity K1 ai_compute: prefer 2.0 TOPS (found 2 TOPS)

zh/k1_muse_pi/root_overview.md

  • Line 43: Product name casing: use 'SpacemiT' not 'spacemit'
  • Line 7: [Warning] Terminology: prefer AI 算力 instead of AI算力
  • Line 23: [Warning] Terminology: prefer AI 算力 instead of AI算力
  • Line 7: [Suggestion] Entity K1 cpu_core_count: prefer 8 核 (found 八核)
  • Line 9: [Suggestion] Entity K1 cpu_core_count: prefer 8 核 (found 八核)
  • Line 10: [Suggestion] Entity K1 ai_compute: prefer 2.0 TOPS (found 2 TOPS)
  • Line 23: [Suggestion] Entity K1 cpu_core_count: prefer 8 核 (found 8核)
  • Line 23: [Suggestion] Entity K1 ai_compute: prefer 2.0 TOPS (found 2 TOPS)
  • Line 7: [Suggestion] Entity MUSE Pi cpu_core_count: prefer 8 核 (found 八核)
  • Line 9: [Suggestion] Entity MUSE Pi cpu_core_count: prefer 8 核 (found 八核)
  • Line 10: [Suggestion] Entity MUSE Pi ai_compute: prefer 2.0 TOPS (found 2 TOPS)
  • Line 23: [Suggestion] Entity MUSE Pi ai_compute: prefer 2.0 TOPS (found 2 TOPS)
  • Line 23: [Suggestion] Entity MUSE Pi cpu_core_count: prefer 8 核 (found 8核)

zh/k1_muse_pi_pro/root_overview.md

  • Line 64: Product name casing: use 'SpacemiT' not 'spacemit'
  • Line 57: [Warning] Terminology: prefer 温度范围 instead of ℃
  • Line 11: [Suggestion] Entity K1 cpu_core_count: prefer 8 核 (found 八核)
  • Line 42: [Suggestion] Entity K1 ai_compute: prefer 2.0 TOPS (found 2 TOPS)
  • Line 11: [Suggestion] Entity MUSE Pi cpu_core_count: prefer 8 核 (found 八核)
  • Line 42: [Suggestion] Entity MUSE Pi ai_compute: prefer 2.0 TOPS (found 2 TOPS)
  • Line 65: Use full-width '?' instead of '?'

zh/k1_muse_shelf/root_overview.md

  • Line 57: Product name casing: use 'SpacemiT' not 'spacemit'
  • Line 51: [Warning] Terminology: prefer 温度范围 instead of ℃
  • Line 18: [Suggestion] Entity K1 cpu_core_count: prefer 8 核 (found 八核)
  • Line 43: [Suggestion] Entity K1 ai_compute: prefer 2.0 TOPS (found 2 TOPS)
  • Line 58: Use full-width '?' instead of '?'

zh/k1_riscv_labkit/root_overview.md

  • Line 51: Product name casing: use 'SpacemiT' not 'spacemit'
  • Line 40: [Warning] Terminology: prefer I²C instead of I2C
  • Line 31: [Suggestion] Entity K1 ai_compute: prefer 2.0 TOPS (found 2 TOPS)

zh/k3_com260/com260_ds.md

  • Line 731: Placeholder found: 'TBD'
  • Line 37: [Warning] Terminology: prefer I²C instead of I2C
  • Line 62: [Warning] Terminology: prefer 温度范围 instead of ˚C
  • Line 184: [Warning] Terminology: prefer I²C instead of I2C
  • Line 188: [Warning] Terminology: prefer I²C instead of I2C
  • Line 189: [Warning] Terminology: prefer I²C instead of I2C
  • Line 190: [Warning] Terminology: prefer I²C instead of I2C
  • Line 191: [Warning] Terminology: prefer I²C instead of I2C
  • Line 344: [Warning] Terminology: prefer I²C instead of I2C
  • Line 346: [Warning] Terminology: prefer I²C instead of I2C
  • Line 347: [Warning] Terminology: prefer I²C instead of I2C
  • Line 350: [Warning] Terminology: prefer I²C instead of I2C
  • Line 351: [Warning] Terminology: prefer I²C instead of I2C
  • Line 352: [Warning] Terminology: prefer I²C instead of I2C
  • Line 353: [Warning] Terminology: prefer I²C instead of I2C
  • Line 354: [Warning] Terminology: prefer I²C instead of I2C
  • Line 355: [Warning] Terminology: prefer I²C instead of I2C
  • Line 358: [Warning] Terminology: prefer I²C instead of I2C
  • Line 362: [Warning] Terminology: prefer I²C instead of I2C
  • Line 363: [Warning] Terminology: prefer I²C instead of I2C
  • Line 364: [Warning] Terminology: prefer I²C instead of I2C
  • Line 365: [Warning] Terminology: prefer I²C instead of I2C
  • Line 389: [Warning] Terminology: prefer I²C instead of I2C
  • Line 390: [Warning] Terminology: prefer I²C instead of I2C
  • Line 391: [Warning] Terminology: prefer I²C instead of I2C
  • Line 392: [Warning] Terminology: prefer I²C instead of I2C
  • Line 393: [Warning] Terminology: prefer I²C instead of I2C
  • Line 394: [Warning] Terminology: prefer I²C instead of I2C
  • Line 395: [Warning] Terminology: prefer I²C instead of I2C
  • Line 396: [Warning] Terminology: prefer I²C instead of I2C
  • Line 399: [Warning] Terminology: prefer I²C instead of I2C
  • Line 400: [Warning] Terminology: prefer I²C instead of I2C
  • Line 402: [Warning] Terminology: prefer I²C instead of I2C
  • Line 403: [Warning] Terminology: prefer I²C instead of I2C
  • Line 407: [Warning] Terminology: prefer I²C instead of I2C
  • Line 408: [Warning] Terminology: prefer I²C instead of I2C
  • Line 409: [Warning] Terminology: prefer I²C instead of I2C
  • Line 410: [Warning] Terminology: prefer I²C instead of I2C
  • Line 411: [Warning] Terminology: prefer I²C instead of I2C
  • Line 412: [Warning] Terminology: prefer I²C instead of I2C
  • Line 413: [Warning] Terminology: prefer I²C instead of I2C
  • Line 414: [Warning] Terminology: prefer I²C instead of I2C
  • Line 416: [Warning] Terminology: prefer I²C instead of I2C
  • Line 417: [Warning] Terminology: prefer I²C instead of I2C
  • Line 479: [Warning] Terminology: prefer I²C instead of I2C
  • Line 481: [Warning] Terminology: prefer I²C instead of I2C
  • Line 482: [Warning] Terminology: prefer I²C instead of I2C
  • Line 485: [Warning] Terminology: prefer I²C instead of I2C
  • Line 486: [Warning] Terminology: prefer I²C instead of I2C
  • Line 487: [Warning] Terminology: prefer I²C instead of I2C
  • Line 488: [Warning] Terminology: prefer I²C instead of I2C
  • Line 499: [Warning] Terminology: prefer I²C instead of I2C
  • Line 525: [Warning] Terminology: prefer I²C instead of I2C
  • Line 526: [Warning] Terminology: prefer I²C instead of I2C
  • Line 527: [Warning] Terminology: prefer I²C instead of I2C
  • Line 528: [Warning] Terminology: prefer I²C instead of I2C
  • Line 529: [Warning] Terminology: prefer I²C instead of I2C
  • Line 530: [Warning] Terminology: prefer I²C instead of I2C
  • Line 531: [Warning] Terminology: prefer I²C instead of I2C
  • Line 534: [Warning] Terminology: prefer I²C instead of I2C
  • Line 535: [Warning] Terminology: prefer I²C instead of I2C
  • Line 537: [Warning] Terminology: prefer I²C instead of I2C
  • Line 538: [Warning] Terminology: prefer I²C instead of I2C
  • Line 542: [Warning] Terminology: prefer I²C instead of I2C
  • Line 543: [Warning] Terminology: prefer I²C instead of I2C
  • Line 545: [Warning] Terminology: prefer I²C instead of I2C
  • Line 546: [Warning] Terminology: prefer I²C instead of I2C
  • Line 547: [Warning] Terminology: prefer I²C instead of I2C
  • Line 548: [Warning] Terminology: prefer I²C instead of I2C
  • Line 609: [Warning] Terminology: prefer I²C instead of I2C
  • Line 612: [Warning] Terminology: prefer I²C instead of I2C
  • Line 617: [Warning] Terminology: prefer I²C instead of I2C
  • Line 618: [Warning] Terminology: prefer I²C instead of I2C
  • Line 619: [Warning] Terminology: prefer I²C instead of I2C
  • Line 620: [Warning] Terminology: prefer I²C instead of I2C
  • Line 623: [Warning] Terminology: prefer I²C instead of I2C
  • Line 627: [Warning] Terminology: prefer I²C instead of I2C
  • Line 628: [Warning] Terminology: prefer I²C instead of I2C
  • Line 630: [Warning] Terminology: prefer I²C instead of I2C
  • Line 654: [Warning] Terminology: prefer I²C instead of I2C
  • Line 655: [Warning] Terminology: prefer I²C instead of I2C
  • Line 656: [Warning] Terminology: prefer I²C instead of I2C
  • Line 674: [Warning] Terminology: prefer I²C instead of I2C
  • Line 676: [Warning] Terminology: prefer I²C instead of I2C
  • Line 679: [Warning] Terminology: prefer I²C instead of I2C
  • Line 681: [Warning] Terminology: prefer I²C instead of I2C
  • Line 682: [Warning] Terminology: prefer I²C instead of I2C
  • Line 75: Use full-width '。' instead of '.'
  • Line 89: Use full-width '。' instead of '.'
  • Line 91: Use full-width '?' instead of '?'
  • Line 285: Use full-width '。' instead of '.'

zh/k3_com260/root_overview.md

  • Line 70: Product name casing: use 'SpacemiT' not 'spacemit'
  • Line 64: [Warning] Terminology: prefer I²C instead of I2C
  • Line 11: [Suggestion] Entity K3 model_size: prefer 30B (found 300 亿)
  • Line 11: [Suggestion] Entity K3 Products model_size: prefer 30B (found 300 亿)

zh/k3_pico/root_overview.md

  • Line 83: Product name casing: use 'SpacemiT' not 'spacemit'
  • Line 44: [Warning] Terminology: prefer I²C instead of I2C
  • Line 51: [Warning] Terminology: prefer I²C instead of I2C
  • Line 55: [Warning] Terminology: prefer 温度范围 instead of ℃
  • Line 19: [Suggestion] Entity K3 model_size: prefer 30B (found 300 亿)
  • Line 19: [Suggestion] Entity K3 Products model_size: prefer 30B (found 300 亿)
  • Line 63: Use full-width '。' instead of '.'

zh/k3_rv2768/root_overview.md

  • Line 62: Product name casing: use 'SpacemiT' not 'spacemit'

zh/k3_shelf/root_overview.md

  • Line 102: Product name casing: use 'SpacemiT' not 'spacemit'
  • Line 58: [Warning] Terminology: prefer 温度范围 instead of ℃
  • Line 89: [Warning] Terminology: prefer 温度范围 instead of ℃

⚠️ This is an automated review. It never blocks merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant