Fix minor typo in concurrent mode reference docs (#2473)

content/docs/concurrent-mode-reference.md

@@ -64,7 +64,7 @@ Blocking Mode only contains a small subset of Concurrent Mode features and is in
 In this example, `ProfileDetails` is waiting for an asynchronous API call to fetch some data. While we wait for `ProfileDetails` and `ProfilePhoto`, we will show the `Loading...` fallback instead. It is important to note that until all children inside `<Suspense>` has loaded, we will continue to show the fallback.
 
 `Suspense` takes two props:
-* **fallback** takes an loading indicator. The fallback is shown until all of the children of the `Suspense` component have finished rendering.
+* **fallback** takes a loading indicator. The fallback is shown until all of the children of the `Suspense` component have finished rendering.
 * **unstable_avoidThisFallback** takes a boolean. It tells React whether to "skip" revealing this boundary during the initial load. This API will likely be removed in a future release.
 
 ### `<SuspenseList>` {#suspenselist}
@@ -200,4 +200,4 @@ const SUSPENSE_CONFIG = { timeoutMs: 2000 };
 
 `useDeferredValue` accepts an **optional Suspense Config** with a `timeoutMs`. This timeout (in milliseconds) tells React how long the deferred value is allowed to lag behind.
 
-React will always try to use a shorter lag when network and device allows it.
+React will always try to use a shorter lag when network and device allows it.