chore(docs): 🧹 remove trailing whitespace from Markdown. (#22369)

* chore(docs): 🧹 remove trailing whitespace from Markdown. Found 2 Markdown files with trailing whitespace. * Update CHANGELOG.md Co-authored-by: Kyle Mathews <mathews.kyle@gmail.com>
gatsbyjs · Mar 19, 2020 · f345985 · f345985
1 parent e0933f8
commit f345985
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 2 deletions.
diff --git a/docs/docs/glossary/markdown.md b/docs/docs/glossary/markdown.md
@@ -26,7 +26,7 @@ You can use Markdown to create documents for [Gatsby](https://www.gatsbyjs.org/)
 <figure class="chart">
   <object data="chart.svg" type="image/svg+xml"></object>
   <figcaption>
-    Developers who love using Gatsby versus those who haven't tried it yet.  
+    Developers who love using Gatsby versus those who haven't tried it yet.
   </figcaption>
 </figure>
 ```

diff --git a/packages/gatsby-design-tokens/CHANGELOG.md b/packages/gatsby-design-tokens/CHANGELOG.md
@@ -34,7 +34,8 @@ See [Conventional Commits](https://conventionalcommits.org) for commit guideline
 
 #### Tokens
 
-This update moves the rudimentary tokens even closer to our current sole target, CSS. This e.g. means that instead of exporting an array of integers for `fontSizes` or `space`, we now provide `rem` values instead (while still making the v1 variants available — but we do have "soft" preferences regarding default units for CSS, which are emphasized by these breaking changes).  
+This update moves the rudimentary tokens even closer to our current sole target, CSS. This e.g. means that instead of exporting an array of integers for `fontSizes` or `space`, we now provide `rem` values instead (while still making the v1 variants available — but we do have "soft" preferences regarding default units for CSS, which are emphasized by these breaking changes).
+
 We currently only consume these tokens in the context of CSS, so let's make things a bit easier there:
 
 - `fontsSizes` exports `rem` values now; old values available at `fontSizesRaw`