facebook · yangshun · Nov 11, 2019 · Nov 11, 2019 · Nov 11, 2019
diff --git a/.github/ISSUE_TEMPLATE/bug.md b/.github/ISSUE_TEMPLATE/bug.md
@@ -24,7 +24,7 @@ about: Submit a bug report to help us improve
 <!--
   How did you expect your project to behave?
   It’s fine if you’re not sure your understanding is correct.
-  Just write down what you thought would happen.
+  Write down what you thought would happen.
 -->
 
 (Write what you thought would happen.)
@@ -35,7 +35,7 @@ about: Submit a bug report to help us improve
   Did something go wrong?
   Is something broken, or not behaving as you expected?
   Describe this section in detail, and attach screenshots if possible.
-  Don't just say "it doesn't work"!
+  Don't only say "it doesn't work"!
 -->
 
 (Write what happened. Add screenshots, if applicable.)

diff --git a/.github/ISSUE_TEMPLATE/feature.md b/.github/ISSUE_TEMPLATE/feature.md
@@ -5,7 +5,7 @@ about: Submit a proposal/request for a new feature
 
 <!--
   Consider requesting the feature on https://docusaurus-2.netlify.com/feedback/ instead.
-  Feature requests on v1 will not be accepted easily as we're focusing on building v2.
+  Feature requests on v1 are more likely to be missed as we're focusing on building v2.
 -->
 
 ## 🚀 Feature

diff --git a/.github/ISSUE_TEMPLATE/proposal.md b/.github/ISSUE_TEMPLATE/proposal.md
@@ -5,7 +5,7 @@ about: Propose a non-trivial change to Docusaurus
 
 <!--
   Consider requesting the feature on https://docusaurus-2.netlify.com/feedback/ instead.
-  Feature requests on v1 will not be accepted easily as we're focusing on building v2.
+  Feature requests on v1 are more likely to be missed as we're focusing on building v2.
 -->
 
 ## 💥 Proposal

diff --git a/CHANGELOG-2.x.md b/CHANGELOG-2.x.md
@@ -69,7 +69,7 @@
 
 ### Features
 
-- Add `<Redirect>` component for easy client side redirect. Example Usage:
+- Add `<Redirect>` component for client side redirect. Example Usage:
 ```js
 import React from 'react';
 import {Redirect} from '@docusaurus/router';

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -162,7 +162,7 @@ In order to accept your pull request, we need you to submit a CLA. You only need
 
 ### What Happens Next?
 
-The core Docusaurus team will be monitoring for pull requests. Do help us by making your pull request easy to review by following the guidelines above.
+The core Docusaurus team will be monitoring for pull requests. Do help us by keeping pull requests consistent by following the guidelines above.
 
 ## Style Guide
 

diff --git a/README.md b/README.md
@@ -43,7 +43,7 @@ Read our [contributing guide](https://github.com/facebook/docusaurus/blob/master
 
 ### Beginner Friendly Bugs
 
-To help you get your feet wet and get you familiar with our contribution process, we have a list of [beginner friendly bugs](https://github.com/facebook/docusaurus/labels/good%20first%20issue) that contain bugs which are fairly easy to fix. This is a great place to get started.
+To help you get your feet wet and get you familiar with our contribution process, we have a list of [beginner friendly bugs](https://github.com/facebook/docusaurus/labels/good%20first%20issue) that  might contain smaller issues to tackle first. This is a great place to get started.
 
 ## Contact
 

diff --git a/admin/extending-remarkable.md b/admin/extending-remarkable.md
@@ -20,7 +20,7 @@ Let's talk a bit more about what is done as part of the parsing stage. The resul
 
 #### Inline tokens
 
-Inline tokens are simple tokens that have text as a child. They are leaf nodes, and do not support having additional tokens within. An example of this might be `_emphasized text_`, which might be represented as a token of type `em` with contents of `emphasized text`.
+Inline tokens are tokens that have text as a child. They are leaf nodes, and do not support having additional tokens within. An example of this might be `_emphasized text_`, which might be represented as a token of type `em` with contents of `emphasized text`.
 
 #### Block tokens
 
@@ -36,7 +36,7 @@ The plain markdown text above would be parsed into three tokens:
 - `text`: Plain text token, with a value of "Hi there".
 - `heading_close`: Marks the end of the heading. In this case, it would also have a `hLevel: 3` prop.
 
-This is a basic example, because it contains a simple `text` token within the opening and closing tags. A common block encountered in markdown is the paragraph, which might be tokenized into a series of tokens such as `paragraph_open`, one or more `text` tokens, `link` tokens (if links are present within the text, for example), and, eventually, a `paragraph_close` token.
+This is a basic example, because it contains a `text` token within the opening and closing tags. A common block encountered in markdown is the paragraph, which might be tokenized into a series of tokens such as `paragraph_open`, one or more `text` tokens, `link` tokens (if links are present within the text, for example), and, eventually, a `paragraph_close` token.
 
 #### Core tokens
 
@@ -48,7 +48,7 @@ After we have parsed everything into tokens, we go to the rendering phase. This
 
 ## Creating a Remarkable Extension
 
-Now that you have a better idea of how parsing/rendering works, we can proceed to create a simple extension that renders heading anchors. First we need to determine if we need to extend the parser, or the renderer. In this case, we're only interested in changing how a heading is rendered to HTML, so we'll just need to override the heading renderers.
+Now that you have a better idea of how parsing/rendering works, we can proceed to create an extension that renders heading anchors. First we need to determine if we need to extend the parser, or the renderer. In this case, we're only interested in changing how a heading is rendered to HTML, so we'll just need to override the heading renderers.
 
 The default heading renderers may look like this (you can refer to the Remarkable source code here):
 

diff --git a/docs/api-pages.md b/docs/api-pages.md
@@ -221,4 +221,4 @@ There are several ways to access the default styles provided for your site. If y
 
 You can provide your own custom styles by adding them anywhere in the `website/static` directory. Any `.css` files you provide in the `static` directory will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.
 
-An easy way to figure out what classes you wish to override or add to is to [start your server locally](api-commands.md) and use your browser's inspect element tool.
+One way to figure out what classes you wish to override or add to is to [start your server locally](api-commands.md) and use your browser's inspect element tool.
diff --git a/docs/api-site-config.md b/docs/api-site-config.md
@@ -27,7 +27,7 @@ Color configurations for the site.
 
 - `primaryColor` is the color used the header navigation bar and sidebars.
 - `secondaryColor` is the color seen in the second row of the header navigation bar when the site window is narrow (including on mobile).
-- Custom color configurations can also be added. For example, if user styles are added with colors specified as `$myColor`, then adding a `myColor` field to `colors` will allow you to easily configure this color.
+- Custom color configurations can also be added. For example, if user styles are added with colors specified as `$myColor`, then adding a `myColor` field to `colors` will allow you to configure this color.
 
 #### `copyright` [string]
 

diff --git a/docs/getting-started-installation.md b/docs/getting-started-installation.md
@@ -8,7 +8,7 @@ Docusaurus was designed from the ground up to be easily installed and used to ge
 
 ## Installing Docusaurus
 
-We have created an easy script that will get all of the infrastructure set up for you:
+We have created a helpful script that will get all of the infrastructure set up for you:
 
 1.  Ensure you have the latest version of [Node](https://nodejs.org/en/download/) installed. We also recommend you install [Yarn](https://yarnpkg.com/en/docs/install) as well.
 

diff --git a/docs/getting-started-publishing.md b/docs/getting-started-publishing.md
@@ -194,7 +194,7 @@ Now, whenever a new commit lands in `master`, CircleCI will run your suite of te
 
 When initially deploying to a `gh-pages` branch using CircleCI, you may notice that some jobs triggered by commits to the `gh-pages` branch fail to run successfully due to a lack of tests (This can also result in chat/slack build failure notifications).
 
-You can work around this easily by:
+You can work around this by:
 - Setting the environment variable `CUSTOM_COMMIT_MESSAGE` flag to the `publish-gh-pages` command with the contents of `[skip ci]`.
 e.g.
 ```bash
@@ -247,7 +247,7 @@ Now, whenever a new commit lands in `master`, Travis CI will run your suite of t
 
 ### Hosting on ZEIT Now
 
-With [ZEIT Now](#using-zeit-now), you can deploy your site easily and connect it to [GitHub](https://zeit.co/github) or [GitLab](https://zeit.co/gitlab) to automatically receive a new deployment every time you push a commit.
+With [ZEIT Now](#using-zeit-now), you can deploy your site and connect it to [GitHub](https://zeit.co/github) or [GitLab](https://zeit.co/gitlab) to automatically receive a new deployment every time you push a commit.
 
 ### Hosting on Netlify
 

diff --git a/docs/getting-started-site-creation.md b/docs/getting-started-site-creation.md
@@ -35,7 +35,7 @@ All of your documentation files should be placed inside the `docs` directory as
 
 To create a fully functional site, you only need to do a few steps:
 
-1.  Add your documentation to the `/docs` directory as `.md` files, ensuring you have the proper [header](api-doc-markdown.md#documents) in each file. The simplest header would be the following, where `id` is the link name (e.g., `docs/intro.html`) and the `title` is the webpage's title.
+1.  Add your documentation to the `/docs` directory as `.md` files, ensuring you have the proper [header](api-doc-markdown.md#documents) in each file. One example header would be the following, where `id` is the link name (e.g., `docs/intro.html`) and the `title` is the webpage's title.
 
     ```yaml
     ---

diff --git a/docs/guides-blog.md b/docs/guides-blog.md
@@ -94,7 +94,7 @@ blogSidebarTitle: { default: 'Recent posts', all: 'All blog posts' },
 
 ## RSS Feed
 
-Docusaurus provides a simple RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically added to your website page's HTML `<HEAD>` tag.
+Docusaurus provides an RSS feed for your blog posts. Both RSS and Atom feed formats are supported. This data is automatically added to your website page's HTML `<HEAD>` tag.
 
 A summary of the post's text is provided in the RSS feed up to the `<!--truncate-->`. If no `<!--truncate-->` tag is found, then all text up to 250 characters is used.
 

diff --git a/docs/guides-custom-pages.md b/docs/guides-custom-pages.md
@@ -13,7 +13,7 @@ You can [start](getting-started-preparation.md#verifying-installation) your loca
 
 ## Adding Other Custom Pages
 
-Docusaurus provides some simple example pages in the `website/pages/en` directory, including `index.js`, `users.js`, and `help.js`. These are good examples to showcase how to create a custom page for Docusaurus.
+Docusaurus provides some helpful example pages in the `website/pages/en` directory, including `index.js`, `users.js`, and `help.js`. These are good examples to showcase how to create a custom page for Docusaurus.
 
 ```bash
 root-directory
@@ -33,7 +33,7 @@ root-directory
     └── static
 ```
 
-Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. More information on how to use the provided components or include your own can be found [here](api-pages.md). Information on how to link to your different pages in the header navigation bar can be found [here](guides-navigation.md).
+You are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. More information on how to use the provided components or include your own can be found [here](api-pages.md). Information on how to link to your different pages in the header navigation bar can be found [here](guides-navigation.md).
 
 > If you want your page to show up in your navigation header, you will need to update `siteConfig.js` to add to the `headerLinks` element. e.g., `{ page: 'about-slash', label: 'About/' }`,
 

diff --git a/docs/guides-navigation.md b/docs/guides-navigation.md
@@ -262,7 +262,7 @@ These are two separate class names so you can have the active styles applied to
 
 ## Secondary On-Page Navigation
 
-We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the `onPageNav` site configuration [option](api-site-config.md#optional-fields) to your `siteConfig.js`.
+We support secondary on-page navigation so you can quickly see the topics associated with a given document. To enable this feature, you need to add the `onPageNav` site configuration [option](api-site-config.md#optional-fields) to your `siteConfig.js`.
 
 ```js
 {

diff --git a/docs/guides-translation.md b/docs/guides-translation.md
@@ -3,7 +3,7 @@ id: translation
 title: Translations & Localization
 ---
 
-Docusaurus allows for easy translation functionality using [Crowdin](https://crowdin.com/). Documentation files written in English are uploaded to Crowdin for translation by users within a community. Top-level pages written with English strings can be translated by wrapping any strings you want to translate in a `<translate>` tag. Other titles and labels will also be found and properly translated.
+Docusaurus allows for useful translation functionality using [Crowdin](https://crowdin.com/). Documentation files written in English are uploaded to Crowdin for translation by users within a community. Top-level pages written with English strings can be translated by wrapping any strings you want to translate in a `<translate>` tag. Other titles and labels will also be found and properly translated.
 
 ## Docusaurus Translation Configurations
 

diff --git a/packages/docusaurus-1.x/README.md b/packages/docusaurus-1.x/README.md
@@ -43,7 +43,7 @@ Read our [contributing guide](https://github.com/facebook/docusaurus/blob/master
 
 ### Beginner Friendly Bugs
 
-To help you get your feet wet and get you familiar with our contribution process, we have a list of [beginner friendly bugs](https://github.com/facebook/docusaurus/labels/good%20first%20issue) that contain bugs which are fairly easy to fix. This is a great place to get started.
+To help you get your feet wet and get you familiar with our contribution process, we have a list of [beginner friendly bugs](https://github.com/facebook/docusaurus/labels/good%20first%20issue) that  might contain smaller issues to tackle first. This is a great place to get started.
 
 ## Contact
 

diff --git a/website-1.x/versioned_docs/version-1.10.x/api-pages.md b/website-1.x/versioned_docs/version-1.10.x/api-pages.md
@@ -222,4 +222,4 @@ There are several ways to access the default styles provided for your site. If y
 
 You can provide your own custom styles by adding them anywhere in the `website/static` directory. Any `.css` files you provide in the `static` directory will get concatenated to the end of Docusaurus' provided styles, allowing you to add to or override Docusaurus default styles as you wish.
 
-An easy way to figure out what classes you wish to override or add to is to [start your server locally](api-commands.md) and use your browser's inspect element tool.
+One way to figure out what classes you wish to override or add to is to [start your server locally](api-commands.md) and use your browser's inspect element tool.
diff --git a/website-1.x/versioned_docs/version-1.10.x/api-site-config.md b/website-1.x/versioned_docs/version-1.10.x/api-site-config.md
@@ -28,7 +28,7 @@ Color configurations for the site.
 
 - `primaryColor` is the color used the header navigation bar and sidebars.
 - `secondaryColor` is the color seen in the second row of the header navigation bar when the site window is narrow (including on mobile).
-- Custom color configurations can also be added. For example, if user styles are added with colors specified as `$myColor`, then adding a `myColor` field to `colors` will allow you to easily configure this color.
+- Custom color configurations can also be added. For example, if user styles are added with colors specified as `$myColor`, then adding a `myColor` field to `colors` will allow you to configure this color.
 
 #### `copyright` [string]
 

diff --git a/website-1.x/versioned_docs/version-1.10.x/getting-started-publishing.md b/website-1.x/versioned_docs/version-1.10.x/getting-started-publishing.md
@@ -188,7 +188,7 @@ Now, whenever a new commit lands in `master`, CircleCI will run your suite of te
 
 When initially deploying to a `gh-pages` branch using CircleCI, you may notice that some jobs triggered by commits to the `gh-pages` branch fail to run successfully due to a lack of tests (This can also result in chat/slack build failure notifications).
 
-You can work around this easily by:
+You can work around this by:
 - Setting the environment variable `CUSTOM_COMMIT_MESSAGE` flag to the `publish-gh-pages` command with the contents of `[skip ci]`.
 e.g.
 ```bash
@@ -241,7 +241,7 @@ Now, whenever a new commit lands in `master`, Travis CI will run your suite of t
 
 ### Hosting on ZEIT Now
 
-With [ZEIT Now](#using-zeit-now), you can deploy your site easily and connect it to [GitHub](https://zeit.co/github) or [GitLab](https://zeit.co/gitlab) to automatically receive a new deployment every time you push a commit.
+With [ZEIT Now](#using-zeit-now), you can deploy your site and connect it to [GitHub](https://zeit.co/github) or [GitLab](https://zeit.co/gitlab) to automatically receive a new deployment every time you push a commit.
 
 ### Hosting on Netlify
 

diff --git a/website-1.x/versioned_docs/version-1.10.x/getting-started-site-creation.md b/website-1.x/versioned_docs/version-1.10.x/getting-started-site-creation.md
@@ -36,7 +36,7 @@ All of your documentation files should be placed inside the `docs` directory as
 
 To create a fully functional site, you only need to do a few steps:
 
-1.  Add your documentation to the `/docs` directory as `.md` files, ensuring you have the proper [header](api-doc-markdown.md#documents) in each file. The simplest header would be the following, where `id` is the link name (e.g., `docs/intro.html`) and the `title` is the webpage's title.
+1.  Add your documentation to the `/docs` directory as `.md` files, ensuring you have the proper [header](api-doc-markdown.md#documents) in each file. One example header would be the following, where `id` is the link name (e.g., `docs/intro.html`) and the `title` is the webpage's title.
 
     ```yaml
     ---

diff --git a/website-1.x/versioned_docs/version-1.10.x/guides-custom-pages.md b/website-1.x/versioned_docs/version-1.10.x/guides-custom-pages.md
@@ -14,7 +14,7 @@ You can [start](getting-started-preparation.md#verifying-installation) your loca
 
 ## Adding Other Custom Pages
 
-Docusaurus provides some simple example pages in the `website/pages/en` directory, including `index.js`, `users.js`, and `help.js`. These are good examples to showcase how to create a custom page for Docusaurus.
+Docusaurus provides some helpful example pages in the `website/pages/en` directory, including `index.js`, `users.js`, and `help.js`. These are good examples to showcase how to create a custom page for Docusaurus.
 
 ```bash
 root-directory
@@ -33,7 +33,7 @@ root-directory
     └── static
 ```
 
-Of course, you are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. More information on how to use the provided components or include your own can be found [here](api-pages.md). Information on how to link to your different pages in the header navigation bar can be found [here](guides-navigation.md).
+You are also free to write your own pages. It is strongly suggested that you at least have an index page, but none of the pages provided are mandatory to include in your site. More information on how to use the provided components or include your own can be found [here](api-pages.md). Information on how to link to your different pages in the header navigation bar can be found [here](guides-navigation.md).
 
 > If you want your page to show up in your navigation header, you will need to update `siteConfig.js` to add to the `headerLinks` element. e.g., `{ page: 'about-slash', label: 'About/' }`,
 

diff --git a/website-1.x/versioned_docs/version-1.10.x/guides-navigation.md b/website-1.x/versioned_docs/version-1.10.x/guides-navigation.md
@@ -263,7 +263,7 @@ These are two separate class names so you can have the active styles applied to
 
 ## Secondary On-Page Navigation
 
-We support secondary on-page navigation so you can more easily see the topics associated with a given document. To enable this feature, you need to add the `onPageNav` site configuration [option](api-site-config.md#optional-fields) to your `siteConfig.js`.
+We support secondary on-page navigation so you can quickly see the topics associated with a given document. To enable this feature, you need to add the `onPageNav` site configuration [option](api-site-config.md#optional-fields) to your `siteConfig.js`.
 
 ```js
 {

diff --git a/website-1.x/versioned_docs/version-1.11.x/api-site-config.md b/website-1.x/versioned_docs/version-1.11.x/api-site-config.md
@@ -28,7 +28,7 @@ Color configurations for the site.
 
 - `primaryColor` is the color used the header navigation bar and sidebars.
 - `secondaryColor` is the color seen in the second row of the header navigation bar when the site window is narrow (including on mobile).
-- Custom color configurations can also be added. For example, if user styles are added with colors specified as `$myColor`, then adding a `myColor` field to `colors` will allow you to easily configure this color.
+- Custom color configurations can also be added. For example, if user styles are added with colors specified as `$myColor`, then adding a `myColor` field to `colors` will allow you to configure this color.
 
 #### `copyright` [string]