</span></code></pre></div></div><p>Words that should be ignored or are unrecognized must be added to the <ahref="./wordlist.txt">wordlist</a>.</p><h2id="markdown-verification"><ahref="#markdown-verification"class="anchor-heading"aria-labelledby="markdown-verification"><svgviewBox="0 0 16 16"aria-hidden="true"><usexlink:href="#svg-link"></use></svg></a> Markdown Verification </h2><p>We use <ahref="https://remark.js.org/">remark</a> to verify our markdown. You can easily run this tool simply by using our <codeclass="language-plaintext highlighter-rouge">npm</code> package:</p><divclass="language-console highlighter-rouge"><divclass="highlight"><preclass="highlight"><code><spanclass="go">npm install
npm run lint
</span></code></pre></div></div><h2id="language-mode"><ahref="#language-mode"class="anchor-heading"aria-labelledby="language-mode"><svgviewBox="0 0 16 16"aria-hidden="true"><usexlink:href="#svg-link"></use></svg></a> Language mode </h2><ul><li>Specifications SHOULD use formal technical language (<em>different from academic language</em>).</li><li>Where appropriate, language SHOULD NOT use personal pronouns.</li><li>Avoid using the <ahref="https://en.wikipedia.org/wiki/English_passive_voice">passive voice</a> when being specific.</li><li>In places where the passive voice is appropriate but makes the subject ambiguous, append the passive voice with “by <codeclass="language-plaintext highlighter-rouge">subject</code>”. Alternatively restructure the sentence to be in the active voice adding the sentence subject.</li></ul><p>For further reading on writing technical documents please read the Google Technical Writing article on <ahref="https://developers.google.com/tech-writing/one/active-voice">Active voice vs. passive voice</a>.</p><details><summary>Examples:</summary> ### Personal pronouns Informal: >In this specification, **we** describe Formal: >This specification describes Informal: >If **you** want to run a Waku node and receive messages from Status clients, it must be properly configured. Formal: >A Waku node must be properly configured to receive messages from Status clients. ### Passive voice Passive voice: >a corresponding confirmation **is broadcast** by one or more peers Active voice: >**one or more peers broadcast** a corresponding confirmation In the case where the object of the sentence needs to be highlighted or given prominence the passive voice is appropriate. However, pay attention to not introduce an ambiguous subject if communicating specific information is your goal. ### Appropriate use of the passive voice >The Batch Acknowledge packet is followed by a keccak256 hash of the envelope's batch data (raw bytes). The subject of the sentence is "a keccak256 hash", but the sentence wants to highlight the Batch Acknowledge. ### Ambiguous subject In many cases sentences written in passive voice may be grammatically correct but hide that the sentence lacks a specified subject. Ambiguous: >A message confirmation **is sent** using Batch Acknowledge Active specific: >**A node sends** a message confirmation using Batch Acknowledge Passive specific: >A message confirmation **is sent by a node** using Batch Acknowledge Notice that the ambiguous sentence infers or omits the subject. Making it unclear what or who performs an action on the object of the sentence. In the example ambiguous sentence it is not stated what or who is sending a message confirmation. </details></div></div><divclass="search-overlay"></div></div></body></html>
