Update README.md (#47)

Use `httpnext` for repo name.

Author: lovelydinosaur

README.md

@@ -16,7 +16,7 @@ We've been trying to handle that incrementally, working from a requests-compatib
 
 This work presents a significantly simplified implementation of `httpx`.
 
-* Seriously, a [radically simplified implementation](https://github.com/encode/httpx-insiders/blob/main/src/httpx/_client.py). While still fulfiling the same set of functionality.<sup>*</sup>
+* Seriously, a [radically simplified implementation](https://github.com/encode/httpx-insiders/blob/main/src/httpx/_client.py). While still fulfiling the same set of functionality.
 * A consistent & tightly typed set of HTTP components, with immutability throughout. Includes URLs, Query Parameters, Headers, Form & File interfaces, all of which are suitable for either client side or server side codebases.
 * A re-engineered [connection pool implementation](https://github.com/encode/httpx-insiders/blob/main/src/httpx/_pool.py), with tighter more obvious concurrency handling.
 * The core networking component is simple enough to be directly included. The only hard dependencies here are `h11` and `truststore`.
@@ -28,16 +28,10 @@ There is also preliminary work ongoing for httpx *for both client-side and serve
 
 # Overview
 
-Installation from the insiders repo...
+Installation...
 
 ```shell
-$ pip install git+https://github.com/encode/httpx-insiders.git
-```
-
-Or the public installation...
-
-```shell
-$ pip install https://staging.d2pg1230p7w6nv.amplifyapp.com/httpx-design-proposal.tar.gz
+$ pip install git+https://github.com/encode/httpnext.git
 ```
 
 Lets get to work...