|
| 1 | +--- |
| 2 | +title: Content standardization |
| 3 | +description: Guide to use consistent terminology in content writing |
| 4 | +lang: en |
| 5 | +--- |
| 6 | + |
| 7 | +This style guide aims to standardize certain aspects of writing content to make the contribution process smoother. |
| 8 | + |
| 9 | +## Use American English {#american-english} |
| 10 | + |
| 11 | +For words that have multiple spellings, use American English over British English. |
| 12 | + |
| 13 | +**For example:** |
| 14 | + |
| 15 | +- "decentralized" over "decentralised" |
| 16 | +- "color" over "colour" |
| 17 | +- "analyze" over "analyse" |
| 18 | + |
| 19 | +## Terminology {#Terminology} |
| 20 | + |
| 21 | +### Ethereum {#ethereum} |
| 22 | + |
| 23 | +Ethereum is a proper noun and should always be capitalized. |
| 24 | + |
| 25 | +- "Ethereum" not "ethereum" |
| 26 | + |
| 27 | +### Ether {#ether} |
| 28 | + |
| 29 | +Ether is a common noun and should not be capitalized unless at the beginning of a sentence. ETH, on the other hand, is a currency abbreviation (and ticker symbol) and should always be capitalized. |
| 30 | + |
| 31 | +- "ether" not "Ether" |
| 32 | +- "ETH" not "eth or Eth" |
| 33 | + |
| 34 | +### Mainnet {#mainnet} |
| 35 | + |
| 36 | +When referring to the Ethereum Mainnet (i.e. not referring to a testnet) use the proper noun. Proper nouns help avoid confusion and build greater understanding. |
| 37 | + |
| 38 | +**Correct usage:** |
| 39 | + |
| 40 | +- Mainnet |
| 41 | +- Ethereum Mainnet |
| 42 | + |
| 43 | +**Incorrect usage:** |
| 44 | + |
| 45 | +- main net |
| 46 | +- mainnet |
| 47 | +- Main net |
| 48 | +- Ethereum mainnet |
| 49 | + |
| 50 | +### Proof-of-work / Proof-of-stake {#proof-of} |
| 51 | + |
| 52 | +Proof-of-work should be capitalized only when at the beginning of a sentence. In any other instance, all letters should be lower case. In either case, proof-of-work should be hyphenated between each word. |
| 53 | + |
| 54 | +**Correct usage:** |
| 55 | + |
| 56 | +- Proof-of-work |
| 57 | +- proof-of-work |
| 58 | + |
| 59 | +**Incorrect usage:** |
| 60 | + |
| 61 | +- Proof-of-Work |
| 62 | +- Proof of work |
| 63 | +- proof of work |
| 64 | + |
| 65 | +The same rules we apply to proof-of-work are applicable to proof-of-stake, proof-of-authority, proof-of-humanity, proof-of-individuality, etc. |
| 66 | + |
| 67 | +### Smart contract {#smart-contract} |
| 68 | + |
| 69 | +Smart contract is a common noun and should only be capitalized at the beginning of a sentence. In any other instance, all letters should be lowercase. |
| 70 | + |
| 71 | +**Correct usage:** |
| 72 | + |
| 73 | +- Smart contract |
| 74 | +- smart contract |
| 75 | + |
| 76 | +** Incorrect usage:** |
| 77 | + |
| 78 | +- Smart Contract |
| 79 | + |
| 80 | +### The Merge {#the-merge} |
| 81 | + |
| 82 | +When referring to The Merge, treat it as a proper noun. Always capitalize the first letter in each word. |
| 83 | + |
| 84 | +**Correct usage:** |
| 85 | + |
| 86 | +- The Merge |
| 87 | + |
| 88 | +**Incorrect usage:** |
| 89 | + |
| 90 | +- The merge |
| 91 | +- the Merge |
| 92 | + |
| 93 | +### Zero-knowledge {#zero-knowledge} |
| 94 | + |
| 95 | +Zero-knowledge is a common noun and should only be capitalized at the beginning of a sentence. In any other instance, all letters should be lowercase. In either case, zero-knowledge should be hyphenated between each word. |
| 96 | + |
| 97 | +**Correct usage:** |
| 98 | + |
| 99 | +- Zero-knowledge |
| 100 | +- zero-knowledge |
| 101 | + |
| 102 | +**Incorrect usage:** |
| 103 | + |
| 104 | +- Zero-Knowledge |
| 105 | +- Zero knowledge |
| 106 | +- zero knowledge |
| 107 | + |
| 108 | +### ZK-proof {#ZK-proof} |
| 109 | + |
| 110 | +When using the abbreviated form of zero-knowledge proof you should shorten zero-knowledge to ZK, and hyphenate the abbreviation. |
| 111 | + |
| 112 | +**Correct usage:** |
| 113 | + |
| 114 | +- ZK-proof |
| 115 | + |
| 116 | +**Incorrect usage:** |
| 117 | + |
| 118 | +- Zk-proof |
| 119 | +- zK-proof |
| 120 | +- zk-proof |
| 121 | +- Zk proof |
| 122 | +- zK proof |
| 123 | +- zk proof |
| 124 | + |
| 125 | +### ZK-rollup {#ZK-rollup} |
| 126 | + |
| 127 | +When using the abbreviated form of zero-knowledge rollup you should shorten zero-knowledge to ZK, and hyphenate the abbreviation. |
| 128 | + |
| 129 | +**Correct usage:** |
| 130 | + |
| 131 | +- ZK-rollup |
| 132 | + |
| 133 | +**Incorrect usage:** |
| 134 | + |
| 135 | +- Zk-rollup |
| 136 | +- zK-rollup |
| 137 | +- zk-rollup |
| 138 | +- Zk rollup |
| 139 | +- zK rollup |
| 140 | +- zk rollup |
| 141 | + |
| 142 | +### Use active voice {#use-active-voice} |
| 143 | + |
| 144 | +Sentences using active voice are more concise and efficient, making your writing more engaging and easier to comprehend. |
| 145 | + |
| 146 | +**Active voice sentence:** an actor acts on a target |
| 147 | + |
| 148 | +> _"The man bought a car."_ |
| 149 | +
|
| 150 | +**Passive voice sentence:** a target acts on an actor |
| 151 | + |
| 152 | +> _"The car was bought by a man."_ |
| 153 | +
|
| 154 | +[Read more on active voice](https://www.grammarly.com/blog/active-vs-passive-voice/) |
| 155 | + |
| 156 | +_This isn't an easy one, especially for non-native English speakers. If you aren't sure, don't worry. We'll help with any of these._ |
| 157 | + |
| 158 | +### Linking to internal pages {#internal-links} |
| 159 | + |
| 160 | +When linking to another page on Ethereum.org, use the relative path over the absolute path. Do not hard-code the language path (i.e. `/en/`) in any links. This maintains consistent functionality across different language versions of the site. |
| 161 | + |
| 162 | +```md |
| 163 | +<!-- Good --> |
| 164 | + |
| 165 | +Read more about [smart contracts](/docs/developers/smart-contracts/) |
| 166 | + |
| 167 | +<!-- Bad --> |
| 168 | + |
| 169 | +Read more about [smart contracts](/en/docs/developers/smart-contracts) |
| 170 | +Read more about [smart contracts](https://ethereum.org/en/docs/developers/smart-contracts) |
| 171 | +``` |
| 172 | + |
| 173 | +Please also add a trailing slash to all links. This keeps links consistent and avoids redirects, which hurts site performance. |
| 174 | + |
| 175 | +```md |
| 176 | +<!-- Good --> |
| 177 | + |
| 178 | +Read more about [smart contracts](/docs/developers/smart-contracts/) |
| 179 | + |
| 180 | +<!-- Bad --> |
| 181 | + |
| 182 | +Read more about [smart contracts](/docs/developers/smart-contracts) |
| 183 | +``` |
| 184 | + |
| 185 | +### Linking to images {#images} |
| 186 | + |
| 187 | +When adding an image to a page, the image should be downloaded and placed in the same folder as the markdown file. You can reference the image like this: |
| 188 | + |
| 189 | +`` |
| 190 | + |
| 191 | +```md |
| 192 | +<!-- Good --> |
| 193 | + |
| 194 | + |
| 195 | + |
| 196 | +<!-- Bad --> |
| 197 | + |
| 198 | + |
| 199 | +``` |
| 200 | + |
| 201 | +This helps us ensure the image will be available. |
| 202 | + |
| 203 | +### Using emojis {#images} |
| 204 | + |
| 205 | +Everyone loves emojis <Emoji text="🥰" size={1} /> To standardize the appearance of all Emojis across browsers, ethereum.org uses an `<Emoji />` React component. |
| 206 | + |
| 207 | +```md |
| 208 | +<--- Good ---> |
| 209 | + |
| 210 | +The London Upgrade is live <Emoji text=":tada:" size={1} /> |
| 211 | + |
| 212 | +The London Upgrade is live <Emoji text="🎉" size={1} /> |
| 213 | + |
| 214 | +<--- Bad ---> |
| 215 | + |
| 216 | +The London Upgrade is live 🎉 |
| 217 | +``` |
| 218 | + |
| 219 | +### Header casing {#header-casing} |
| 220 | + |
| 221 | +This site uses **sentence casing** for header names as a convention. Only the first word and proper nouns are capitalized. This applies to all markdown files on lines that begin with hashes (#). |
| 222 | + |
| 223 | +```md |
| 224 | +<!-- Good --> |
| 225 | + |
| 226 | +## Minting your NFT |
| 227 | + |
| 228 | +### Setting up your wallet |
| 229 | + |
| 230 | +### Get enough ether |
| 231 | + |
| 232 | +<!-- Bad --> |
| 233 | + |
| 234 | +## Minting Your NFT |
| 235 | + |
| 236 | +### Setting Up Your Wallet |
| 237 | + |
| 238 | +### Getting Enough Ether |
| 239 | +``` |
| 240 | + |
| 241 | +### Article authors {#authors} |
| 242 | + |
| 243 | +When citing articles from a specific author or organization, use the article's name as a link, followed by a dash, then the author's name italicized. |
| 244 | + |
| 245 | +```md |
| 246 | +<--- Good ---> |
| 247 | + |
| 248 | +- [A rollup-centric ethereum roadmap](https://ethereum-magicians.org/t/a-rollup-centric-ethereum-roadmap/4698) — _Vitalik Buterin_ |
| 249 | +- [The History of Ethereum Testnets](https://consensys.net/blog/news/the-history-of-ethereum-testnets/) – _ConsenSys_ |
| 250 | + |
| 251 | +<--- Bad---> |
| 252 | + |
| 253 | +- [A rollup-centric ethereum roadmap by Vitalik Buterin](https://ethereum-magicians.org/t/a-rollup-centric-ethereum-roadmap/4698) |
| 254 | +- [ConsenSys on The History of Ethereum Testnets](https://consensys.net/blog/news/the-history-of-ethereum-testnets/) – _ConsenSys_ |
| 255 | +``` |
0 commit comments