fix: Enable remark-lint-no-trailing-spaces

.editorconfig

@@ -9,8 +9,5 @@ end_of_line = lf
 insert_final_newline = true
 trim_trailing_whitespace = true
 
-[*.md]
-trim_trailing_whitespace = false
-
 [*.svg]
 insert_final_newline = false

.remarkrc

@@ -8,7 +8,6 @@
     ["remark-lint-maximum-line-length", false],
     ["remark-lint-no-file-name-articles", false],
     ["remark-lint-no-literal-urls", false],
-    ["remark-lint-no-trailing-spaces", false],
     ["remark-lint-no-undefined-references", false],
     ["remark-lint-prohibited-strings", false],
     ["remark-preset-lint-node/remark-lint-nodejs-links", false]

TRANSLATION.md

@@ -17,7 +17,7 @@ Original source can be found in [/locale/en](https://github.com/nodejs/nodejs.or
 
 ### Can't find my locale on Crowdin
 
-Please create a [new issue](https://github.com/nodejs/nodejs.org/issues/new?template=03-i18n.md) in this repo. Crowdin managers team would be happy to add new languages. 
+Please create a [new issue](https://github.com/nodejs/nodejs.org/issues/new?template=03-i18n.md) in this repo. Crowdin managers team would be happy to add new languages.
 
 ## Localization groups
 

locale/en/black-lives-matter.md

@@ -91,9 +91,9 @@ layout: black-lives-matter.hbs
 * William Green
 * Willie McCoy
 * Yassin Mohamed
-* …[and](https://mappingpoliceviolence.org/) [countless](https://twitter.com/samswey/status/1259254114606886913) 
-  [more](https://en.wikipedia.org/wiki/Lists_of_killings_by_law_enforcement_officers_in_the_United_States#Lists_of_killings) 
-  [lives](https://ebwiki.org/) 
+* …[and](https://mappingpoliceviolence.org/) [countless](https://twitter.com/samswey/status/1259254114606886913)
+  [more](https://en.wikipedia.org/wiki/Lists_of_killings_by_law_enforcement_officers_in_the_United_States#Lists_of_killings)
+  [lives](https://ebwiki.org/)
   not listed  here, taken by violence and brutality.
 
 </section>

locale/en/blog/release/v14.15.2.md

@@ -10,7 +10,7 @@ author: Bethany Nicolle Griggs
 
 ### Notable Changes
 
-* **deps**: 
+* **deps**:
   * upgrade npm to 6.14.9 (Myles Borins) [#36450](https://github.com/nodejs/node/pull/36450)
   * update acorn to v8.0.4 (Michaël Zasso) [#35791](https://github.com/nodejs/node/pull/35791)
 * **doc**: add release key for Danielle Adams (Danielle Adams) [#35545](https://github.com/nodejs/node/pull/35545)

locale/en/blog/vulnerability/april-2020-openssl-updates.md

@@ -37,7 +37,7 @@ is "HIGH" severity under their
 meaning they are:
 
 > ... issues that are of a lower risk than critical, perhaps due to affecting
-> less common configurations, or which are less likely to be exploitable. 
+> less common configurations, or which are less likely to be exploitable.
 
 All supported versions of Node.js use OpenSSL v1.1.1, therefore all active
 release lines are impacted by this update: v10.x, v12.x, v13.x, and v14.x (

locale/en/blog/vulnerability/february-2021-security-releases.md

@@ -22,7 +22,7 @@ Thank you to OMICRON electronics for reporting this vulnerability.
 
 ### DNS rebinding in --inspect (CVE-2021-22884)
 
-Affected Node.js versions are vulnerable to a DNS rebinding attack when the whitelist includes “localhost6”. When “localhost6” is not present in /etc/hosts, it is just an ordinary domain that is resolved via DNS, i.e., over network. If the attacker controls the victim's DNS server or can spoof its responses, the DNS rebinding protection can be bypassed by using the “localhost6” domain. As long as the attacker uses the “localhost6” domain, they can still apply the attack described in CVE-2018-7160. 
+Affected Node.js versions are vulnerable to a DNS rebinding attack when the whitelist includes “localhost6”. When “localhost6” is not present in /etc/hosts, it is just an ordinary domain that is resolved via DNS, i.e., over network. If the attacker controls the victim's DNS server or can spoof its responses, the DNS rebinding protection can be bypassed by using the “localhost6” domain. As long as the attacker uses the “localhost6” domain, they can still apply the attack described in CVE-2018-7160.
 
 Impacts:
 * All versions of the 15.x, 14.x, 12.x and 10.x releases lines

locale/en/download/package-manager.md

@@ -207,7 +207,7 @@ pkgin -y install nodejs
 
 ## Nodenv
 
-`nodenv` is a lightweight node version manager, similar to `nvm`. It's simple and predictable. A rich plugin ecosystem lets you tailor it to suit your needs. Use `nodenv` to pick a Node version for your application and guarantee that your development environment matches production. 
+`nodenv` is a lightweight node version manager, similar to `nvm`. It's simple and predictable. A rich plugin ecosystem lets you tailor it to suit your needs. Use `nodenv` to pick a Node version for your application and guarantee that your development environment matches production.
 
 Nodenv installation instructions are maintained [on its Github page](https://github.com/nodenv/nodenv#installation). Please visit that page to ensure you're following the latest version of the installation steps.
 
@@ -301,7 +301,7 @@ pkg_add node
 
 Node.js is available in the main repositories under the following packages:
 
-* **openSUSE Leap 15.2**: `nodejs10`, `nodejs12`, `nodejs14` 
+* **openSUSE Leap 15.2**: `nodejs10`, `nodejs12`, `nodejs14`
 * **openSUSE Tumbleweed**: `nodejs16`
 * **SUSE Linux Enterprise Server (SLES) 12**: `nodejs10`, `nodejs12`, and `nodejs14`
   (The "Web and Scripting Module" must be [enabled](https://www.suse.com/releasenotes/x86_64/SUSE-SLES/12-SP5/#intro-modulesExtensionsRelated).)
@@ -376,4 +376,3 @@ IBM® SDK for Node.js - z/OS® is available in two installation formats,
 SMP/E and PAX. Select the installation format that applies to you:
 * [Installing and configuring SMP/E edition of Node.js on z/OS](https://www.ibm.com/support/knowledgecenter/SSTRRS_14.0.0/com.ibm.nodejs.zos.v14.doc/smpe.htm)
 * [Installing and configuring PAX edition of Node.js on z/OS](https://www.ibm.com/support/knowledgecenter/SSTRRS_14.0.0/com.ibm.nodejs.zos.v14.doc/paxz.htm)
-

locale/es/docs/guides/buffer-constructor-deprecation.md

@@ -173,9 +173,7 @@ _Note that the same applies to `new Buffer()` usage without zero-filling, depend
 
 ## FAQ
 
-### <!--design-flaws-->What is wrong with the 
-
-`Buffer` constructor?
+### <!--design-flaws-->What is wrong with the `Buffer` constructor?
 
 The `Buffer` constructor could be used to create a buffer in many different ways:
 
@@ -213,8 +211,6 @@ Both of these scenarios are considered serious security issues in a real-world w
 
 When using `Buffer.from(req.body.string)` instead, passing a number will always throw an exception instead, giving a controlled behavior that can always be handled by the program.
 
-### <!--ecosystem-usage-->The 
-
-`Buffer()` constructor has been deprecated for a while. Is this really an issue?
+### <!--ecosystem-usage-->The `Buffer()` constructor has been deprecated for a while. Is this really an issue?
 
 Surveys of code in the `npm` ecosystem have shown that the `Buffer()` constructor is still widely used. This includes new code, and overall usage of such code has actually been *increasing*.

locale/fr/docs/guides/buffer-constructor-deprecation.md

@@ -173,9 +173,7 @@ _Note that the same applies to `new Buffer()` usage without zero-filling, depend
 
 ## FAQ
 
-### <!--design-flaws-->What is wrong with the 
-
-`Buffer` constructor?
+### <!--design-flaws-->What is wrong with the `Buffer` constructor?
 
 The `Buffer` constructor could be used to create a buffer in many different ways:
 
@@ -213,8 +211,6 @@ Both of these scenarios are considered serious security issues in a real-world w
 
 When using `Buffer.from(req.body.string)` instead, passing a number will always throw an exception instead, giving a controlled behavior that can always be handled by the program.
 
-### <!--ecosystem-usage-->The 
-
-`Buffer()` constructor has been deprecated for a while. Is this really an issue?
+### <!--ecosystem-usage-->The `Buffer()` constructor has been deprecated for a while. Is this really an issue?
 
 Surveys of code in the `npm` ecosystem have shown that the `Buffer()` constructor is still widely used. This includes new code, and overall usage of such code has actually been *increasing*.

locale/ko/docs/guides/debugging-getting-started.md

@@ -208,7 +208,7 @@ Node 인스펙터에 접속할 수 있는 여러 상용 도구와 오픈소스 
 
 * `Debug` 뷰에서 Node.js 디버그 설정을 실행하거나 `F5` 키를 누르세요.
   [자세한 방법은 여기를 참고하세요.](https://medium.com/gitpod/debugging-node-js-applications-in-theia-76c94c76f0a1)
-  
+
 ### [Eclipse IDE](https://eclipse.org/eclipseide)와 Eclipse Wild Web Developer 확장 프로그램
 
 * .js 파일에서 "Debug As... > Node program"을 선택하거나,

locale/pt-br/knowledge/command-line/how-to-prompt-for-command-line-input.md

@@ -1,5 +1,5 @@
 ---
-title: Como solicitar entrada do usuário a partir de um script de linha de comando? 
+title: Como solicitar entrada do usuário a partir de um script de linha de comando?
 date: '2011-08-26T10:08:50.000Z'
 tags:
   - javascript

locale/ro/docs/guides/buffer-constructor-deprecation.md

@@ -173,9 +173,7 @@ _Note that the same applies to `new Buffer()` usage without zero-filling, depend
 
 ## FAQ
 
-### <!--design-flaws-->What is wrong with the 
-
-`Buffer` constructor?
+### <!--design-flaws-->What is wrong with the `Buffer` constructor?
 
 The `Buffer` constructor could be used to create a buffer in many different ways:
 
@@ -213,8 +211,6 @@ Both of these scenarios are considered serious security issues in a real-world w
 
 When using `Buffer.from(req.body.string)` instead, passing a number will always throw an exception instead, giving a controlled behavior that can always be handled by the program.
 
-### <!--ecosystem-usage-->The 
-
-`Buffer()` constructor has been deprecated for a while. Is this really an issue?
+### <!--ecosystem-usage-->The `Buffer()` constructor has been deprecated for a while. Is this really an issue?
 
 Surveys of code in the `npm` ecosystem have shown that the `Buffer()` constructor is still widely used. This includes new code, and overall usage of such code has actually been *increasing*.