Skip to content
This repository was archived by the owner on Feb 12, 2024. It is now read-only.

Commit 9852d14

Browse files
kvutienkvutienachingbrain
authored
docs: improve README of browser-create-react-app (#3737)
Co-authored-by: kvutien <[email protected]> Co-authored-by: Alex Potsides <[email protected]>
1 parent 8bcf56f commit 9852d14

File tree

1 file changed

+7
-8
lines changed

1 file changed

+7
-8
lines changed

examples/browser-create-react-app/README.md

+7-8
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
## IPFS React app
22

3-
A minimal demonstration of how to use js-ipfs in a `create-react-app` generated app.
3+
This is a minimal demonstration of how to use `js-ipfs` in a `create-react-app` generated app.
44

5-
It boots up a js-ipfs instance (an IPFS node) via a custom React hook in `./src/hooks/use-ipfs-factory.js`, which is called from `./src/App.js`. Once the IPFS node is set up, `App.js` displays its ident and its version number.
5+
It boots up a `js-ipfs` instance (an IPFS node) via a custom React hook in `./src/hooks/use-ipfs-factory.js`, which is called from `./src/App.js`. Once the IPFS node is set up, `./src/App.js` displays the [PeerId](https://docs.libp2p.io/concepts/peer-id/) of this node and the version number of `js-ipfs` used to spawn it.
66

7-
> _Remember that a Peer ID of an IPFS node is [the multihash of the public key of this node](https://github.com/libp2p/specs/blob/master/peer-ids/peer-ids.md#peer-ids), and the public-private key pair of a node is generated by typing `ipfs init`._
7+
> _Side note: The PeerId of the IPFS node is [the multihash of the public key of this node](https://github.com/libp2p/specs/blob/master/peer-ids/peer-ids.md#peer-ids). The public-private key pair of a node is generated by typing `ipfs init`._
88
99
![Screen shot of the js ipfs node id info](./images/screenshot.png)
1010

@@ -23,14 +23,14 @@ $ npm start
2323
```
2424
## Call structure in `App.js`
2525
All React applications store their main logic in `App.js`:
26-
* `App.js` renders the cosmetics of the demo and call `useIpfs` to retrieve the `id` of the node
26+
* `App.js` renders the cosmetics of the demo and calls `useIpfs` to retrieve the `id` of the node
2727
* `useIpfsFactory.js` initialises and closes the IPFS local node
2828
* `useIpfs.js` does the actual calls to IPFS to retrieve the property specified in argument (here the retrieved property is `id`, requested from `App.js`)
2929

3030
## Annexes
31-
### Console message `[HMR] Waiting for update signal from WDS...`
31+
### You may be puzzled by a console message `[HMR] Waiting for update signal from WDS...`
3232

33-
This message comes from the hot reload capability of webpack, that can update the web app every time you save your development code. To remove it, see here: https://stackoverflow.com/questions/59695102/reactjs-console-error-hmr-waiting-for-update-signal-from-wds
33+
This message comes from the hot reload capability of `webpack`, that can update the web app every time you save your development code. To remove it, see here: https://stackoverflow.com/questions/59695102/reactjs-console-error-hmr-waiting-for-update-signal-from-wds
3434

3535
### Available Scripts from create-react-app
3636

@@ -64,5 +64,4 @@ But with modern hosting services like Heroku, Netlity or Fleek, you can skip the
6464

6565
You can learn more on IPFS API in the [IPFS documentation](https://docs.ipfs.io/) and [IPFS npm documentation](https://www.npmjs.com/package/ipfs-http-client).
6666

67-
Details how to use the File System abstraction of IPFS (add, cat, egt, ls etc.) are [here](https://github.com/ipfs/js-ipfs/blob/master/docs/core-api/FILES.md)
68-
67+
Details how to use the File System abstraction of IPFS (add, cat, get, ls etc.) are [here](https://github.com/ipfs/js-ipfs/blob/master/docs/core-api/FILES.md)

0 commit comments

Comments
 (0)