resolve discussions

facebook · Jan 31, 2020 · 582e99c · 582e99c
1 parent c714c47
commit 582e99c
Show file tree

Hide file tree

Showing 8 changed files with 8 additions and 8 deletions.
diff --git a/website/docs/markdown-features.mdx b/website/docs/markdown-features.mdx
@@ -128,7 +128,7 @@ image: https://i.imgur.com/mErPwqL.png
 
 Docusaurus has built-in support for [MDX](https://mdxjs.com), which allows you to write JSX within your Markdown files and render them as React components.
 
-**Note 1:** While both `.md` and `.mdx` files are parsed using MDX, some of the syntax are treated slightly differently. For the most accurate parsing and better editor support, we recommend using the `.mdx` extension for files containing MDX syntax. Let's rename the previous file to `greeting.mdx`
+**Note 1:** While both `.md` and `.mdx` files are parsed using MDX, some of the syntax are treated slightly differently. For the most accurate parsing and better editor support, we recommend using the `.mdx` extension for files containing MDX syntax. Let's rename the previous file to `greeting.mdx`.
 
 **Note 2:** Since all doc files are parsed using MDX, any HTML is treated as JSX. Therefore, if you need to inline-style a component, follow JSX flavor and provide style objects. This behavior is different from Docusaurus 1. See also [Migrating from v1 to v2](./migrating-from-v1-to-v2.md#convert-style-attributes-to-style-objects-in-mdx).
 

diff --git a/website/docs/migrating-from-v1-to-v2.md b/website/docs/migrating-from-v1-to-v2.md
@@ -675,7 +675,7 @@ website
 │   └── version-1.0.0-sidebars.json
 ```
 
-### Convert style attributes to style objects in mdx
+### Convert style attributes to style objects in MDX
 
 Docusaurus 2 uses JSX for doc files. If you have any style attributes in your Docusaurus 1 docs, convert them to style objects, like this:
 

diff --git a/website/versioned_docs/version-2.0.0-alpha.38/markdown-features.mdx b/website/versioned_docs/version-2.0.0-alpha.38/markdown-features.mdx
@@ -128,7 +128,7 @@ image: https://i.imgur.com/mErPwqL.png
 
 Docusaurus has built-in support for [MDX](https://mdxjs.com), which allows you to write JSX within your Markdown files and render them as React components.
 
-**Note 1:** While both `.md` and `.mdx` files are parsed using MDX, some of the syntax are treated slightly differently. For the most accurate parsing and better editor support, we recommend using the `.mdx` extension for files containing MDX syntax. Let's rename the previous file to `greeting.mdx`
+**Note 1:** While both `.md` and `.mdx` files are parsed using MDX, some of the syntax are treated slightly differently. For the most accurate parsing and better editor support, we recommend using the `.mdx` extension for files containing MDX syntax. Let's rename the previous file to `greeting.mdx`.
 
 **Note 2:** Since all doc files are parsed using MDX, any HTML is treated as JSX. Therefore, if you need to inline-style a component, follow JSX flavor and provide style objects. This behavior is different from Docusaurus 1. See also [Migrating from v1 to v2](./migrating-from-v1-to-v2.md#convert-style-attributes-to-style-objects-in-mdx).
 

diff --git a/website/versioned_docs/version-2.0.0-alpha.38/migrating-from-v1-to-v2.md b/website/versioned_docs/version-2.0.0-alpha.38/migrating-from-v1-to-v2.md
@@ -665,7 +665,7 @@ website
 │   └── version-1.0.0-sidebars.json
 ```
 
-### Convert style attributes to style objects in mdx
+### Convert style attributes to style objects in MDX
 
 Docusaurus 2 uses JSX for doc files. If you have any style attributes in your Docusaurus 1 docs, convert them to style objects, like this:
 

diff --git a/website/versioned_docs/version-2.0.0-alpha.39/markdown-features.mdx b/website/versioned_docs/version-2.0.0-alpha.39/markdown-features.mdx
@@ -128,7 +128,7 @@ image: https://i.imgur.com/mErPwqL.png
 
 Docusaurus has built-in support for [MDX](https://mdxjs.com), which allows you to write JSX within your Markdown files and render them as React components.
 
-**Note 1:** While both `.md` and `.mdx` files are parsed using MDX, some of the syntax are treated slightly differently. For the most accurate parsing and better editor support, we recommend using the `.mdx` extension for files containing MDX syntax. Let's rename the previous file to `greeting.mdx`
+**Note 1:** While both `.md` and `.mdx` files are parsed using MDX, some of the syntax are treated slightly differently. For the most accurate parsing and better editor support, we recommend using the `.mdx` extension for files containing MDX syntax. Let's rename the previous file to `greeting.mdx`.
 
 **Note 2:** Since all doc files are parsed using MDX, any HTML is treated as JSX. Therefore, if you need to inline-style a component, follow JSX flavor and provide style objects. This behavior is different from Docusaurus 1. See also [Migrating from v1 to v2](./migrating-from-v1-to-v2.md#convert-style-attributes-to-style-objects-in-mdx).
 

diff --git a/website/versioned_docs/version-2.0.0-alpha.39/migrating-from-v1-to-v2.md b/website/versioned_docs/version-2.0.0-alpha.39/migrating-from-v1-to-v2.md
@@ -665,7 +665,7 @@ website
 │   └── version-1.0.0-sidebars.json
 ```
 
-### Convert style attributes to style objects in mdx
+### Convert style attributes to style objects in MDX
 
 Docusaurus 2 uses JSX for doc files. If you have any style attributes in your Docusaurus 1 docs, convert them to style objects, like this:
 

diff --git a/website/versioned_docs/version-2.0.0-alpha.40/markdown-features.mdx b/website/versioned_docs/version-2.0.0-alpha.40/markdown-features.mdx
@@ -128,7 +128,7 @@ image: https://i.imgur.com/mErPwqL.png
 
 Docusaurus has built-in support for [MDX](https://mdxjs.com), which allows you to write JSX within your Markdown files and render them as React components.
 
-**Note 1:** While both `.md` and `.mdx` files are parsed using MDX, some of the syntax are treated slightly differently. For the most accurate parsing and better editor support, we recommend using the `.mdx` extension for files containing MDX syntax. Let's rename the previous file to `greeting.mdx`
+**Note 1:** While both `.md` and `.mdx` files are parsed using MDX, some of the syntax are treated slightly differently. For the most accurate parsing and better editor support, we recommend using the `.mdx` extension for files containing MDX syntax. Let's rename the previous file to `greeting.mdx`.
 
 **Note 2:** Since all doc files are parsed using MDX, any HTML is treated as JSX. Therefore, if you need to inline-style a component, follow JSX flavor and provide style objects. This behavior is different from Docusaurus 1. See also [Migrating from v1 to v2](./migrating-from-v1-to-v2.md#convert-style-attributes-to-style-objects-in-mdx).
 

diff --git a/website/versioned_docs/version-2.0.0-alpha.40/migrating-from-v1-to-v2.md b/website/versioned_docs/version-2.0.0-alpha.40/migrating-from-v1-to-v2.md
@@ -675,7 +675,7 @@ website
 │   └── version-1.0.0-sidebars.json
 ```
 
-### Convert style attributes to style objects in mdx
+### Convert style attributes to style objects in MDX
 
 Docusaurus 2 uses JSX for doc files. If you have any style attributes in your Docusaurus 1 docs, convert them to style objects, like this: