Remove the "Why JSX?" guide

jamesplease · Feb 8, 2018 · fd76a32 · fd76a32
1 parent 711b924
commit fd76a32
Show file tree

Hide file tree

Showing 3 changed files with 0 additions and 145 deletions.
diff --git a/README.md b/README.md
@@ -55,7 +55,6 @@ yarn add react-request
   * [clearRequestCache()](#clearrequestcache)
   * [clearResponseCache()](#clearresponsecache)
 * [Guides ⇗](./docs/guides/INDEX.md)
-  * [Why JSX? ⇗](./docs/guides/why-jsx.md)
   * [Using the `lazy` Prop ⇗](./docs/guides/using-the-lazy-prop.md)
   * [Aborting ⇗](./docs/guides/aborting.md)
   * [Differences with `fetch()` ⇗](./docs/guides/differences-with-fetch.md)

diff --git a/docs/FAQ.md b/docs/FAQ.md
@@ -11,8 +11,6 @@ request deduplication and response caching) map nicely to the component lifecycl
 of difficult-to-test imperative code from your application by declaratively specifying how you want your requests to
 behave through JSX.
 
-We wrote [a guide](./guides/why-jsx.md) that goes into this answer in greater detail.
-
 #### If a request is made when the component mounts, how does that work for POST, PATCH, or DELETE requests?
 
 The default behavior is that requests are only made on mount for `GET` requests when the component mounts, but

diff --git a/docs/guides/why-jsx.md b/docs/guides/why-jsx.md