From 0facd6a846c1fdacf6bc72473f1155ea343d9e5c Mon Sep 17 00:00:00 2001 From: Gusarich Date: Mon, 22 Sep 2025 19:19:57 +0300 Subject: [PATCH 1/3] feat: mention american english in short style-guide --- contribute/style-guide.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/contribute/style-guide.mdx b/contribute/style-guide.mdx index 7b0714d8..f33e15d1 100644 --- a/contribute/style-guide.mdx +++ b/contribute/style-guide.mdx @@ -108,6 +108,7 @@ Each safety callout should briefly state the risk, scope, rollback/recovery (if ## Terminology and names +* Use American English spelling (for example, color instead of colour). American English is more common. * Use the project term bank for canonical spellings, casing, and preferred terms. One vocabulary prevents drift. Examples: TON, jetton, smart contract, BoC (bag of cells), AccountChain, ShardChain, WorkChain, MasterChain, BaseChain. * Prefer allowlist and denylist over whitelist and blacklist. These are clearer and inclusive. @@ -122,7 +123,7 @@ Each safety callout should briefly state the risk, scope, rollback/recovery (if ## Accessibility -* Use plain English; avoid idioms and culture‑specific references. +* Use plain American English; avoid idioms and culture‑specific references. * Write descriptive headings and link text. * Tables should have headers and units (for example, “Latency (ms)”) and keep cells brief. * Provide text alternatives for complex figures when possible. From 4b37247453665a4821557d64a6fc091183869391 Mon Sep 17 00:00:00 2001 From: Gusarich Date: Mon, 22 Sep 2025 19:31:59 +0300 Subject: [PATCH 2/3] fix: review --- contribute/style-guide.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/contribute/style-guide.mdx b/contribute/style-guide.mdx index f33e15d1..440368df 100644 --- a/contribute/style-guide.mdx +++ b/contribute/style-guide.mdx @@ -123,7 +123,8 @@ Each safety callout should briefly state the risk, scope, rollback/recovery (if ## Accessibility -* Use plain American English; avoid idioms and culture‑specific references. +* Use plain English; avoid idioms and culture-specific references. +* Use American English spelling (e.g., color, analyze). * Write descriptive headings and link text. * Tables should have headers and units (for example, “Latency (ms)”) and keep cells brief. * Provide text alternatives for complex figures when possible. From 286236b6e44235b7405266330c35cf69063e0701 Mon Sep 17 00:00:00 2001 From: Gusarich Date: Mon, 22 Sep 2025 19:33:34 +0300 Subject: [PATCH 3/3] fix: review --- contribute/style-guide.mdx | 1 - 1 file changed, 1 deletion(-) diff --git a/contribute/style-guide.mdx b/contribute/style-guide.mdx index 440368df..8e05ad0d 100644 --- a/contribute/style-guide.mdx +++ b/contribute/style-guide.mdx @@ -108,7 +108,6 @@ Each safety callout should briefly state the risk, scope, rollback/recovery (if ## Terminology and names -* Use American English spelling (for example, color instead of colour). American English is more common. * Use the project term bank for canonical spellings, casing, and preferred terms. One vocabulary prevents drift. Examples: TON, jetton, smart contract, BoC (bag of cells), AccountChain, ShardChain, WorkChain, MasterChain, BaseChain. * Prefer allowlist and denylist over whitelist and blacklist. These are clearer and inclusive.