From 07bb013f9f14bcabe9d68324cfe9b2d7d419269a Mon Sep 17 00:00:00 2001
From: davidblnc <40642621+davidblnc@users.noreply.github.com>
Date: Fri, 9 Oct 2020 14:44:28 +0200
Subject: [PATCH] Add missing word to latest blog post (#3320)

* Add missing word to latest blog post

* Change sentence to past tense
---
 content/blog/2020-09-22-introducing-the-new-jsx-transform.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/blog/2020-09-22-introducing-the-new-jsx-transform.md b/content/blog/2020-09-22-introducing-the-new-jsx-transform.md
index 7999fd9c..73ffce11 100644
--- a/content/blog/2020-09-22-introducing-the-new-jsx-transform.md
+++ b/content/blog/2020-09-22-introducing-the-new-jsx-transform.md
@@ -54,7 +54,7 @@ function App() {
 
 However, this is not perfect:
 
-* Because JSX compiled into `React.createElement`, `React` needed to be in scope if you use JSX.
+* Because JSX was compiled into `React.createElement`, `React` needed to be in scope if you used JSX.
 * There are some [performance improvements and simplifications](https://github.com/reactjs/rfcs/blob/createlement-rfc/text/0000-create-element-changes.md#motivation) that `React.createElement` does not allow.
 
 To solve these issues, React 17 introduces two new entry points to the React package that are intended to only be used by compilers like Babel and TypeScript. Instead of transforming JSX to `React.createElement`, **the new JSX transform** automatically imports special functions from those new entry points in the React package and calls them.