diff --git a/README.md b/README.md
index 42b47f339a6eaf12be9a2ee0fee2575db3c62ea0..0467404296eb564e033d92d24fb1ed2394ab4744 100644
--- a/README.md
+++ b/README.md
@@ -149,7 +149,7 @@ There's just one tier - free - and you need more than 1 XX to get in even for th
 
 The second item is the JUNK asset; that ID is real (it's 5, on xx Chain) and we have two service tiers: standard (0.5 JUNK required) and premium (1 JUNK required). (Just FYI, JUNK is not a divisible asset so you can't have 0.5; anyone who has any will have 1 or more. Just make sure you compare like vs. like in JS.)
 
-Note that this JSON is currently **NOT used** in actual gating checks which are two, as I've mentioned earlier. To save you time, we check for > 1 XX or > 1 JUNK:
+Note that this JSON is currently **NOT used** in actual gating checks which are two, as I've mentioned earlier. To save you time, we check for > 1 XX or >=1 JUNK:
 
 `(accountInfo.data.free.gt(new BN(1_000_000_000)) || assetBalance >= 1)`
 
@@ -157,9 +157,9 @@ If XX and one "hard-coded" asset ID is enough, just change the assetId and minim
 
 While that may work for many single-app sites, [issue #2](https://github.com/armchairancap/polkadot-js-tokengated-website/issues/2) is meant to help some more complex use cases, so this JSON config has been added. 
 
-If you rely on `NEXT_PUBLIC_TOKEN_ASSET_CFG` you will need to change code logic to loop through the list of XX and asset(s) and for assets look up the balance of each. I don't know what people may want to do with this and how (combination of several assets, one asset per route...), so I've just made examples of looping and checking against all assets. But for now the checks remain as mentioned above - i.e. JSON values are ignored.
+If you rely on `NEXT_PUBLIC_TOKEN_ASSET_CFG` you will need to change code logic to loop through the list of XX and asset(s) and for assets look up the balance of each. I don't know what people may want to do with this and how (combination of several assets, one asset per route...), so I've just made examples of looping and checking against all assets. But for now the checks remain as mentioned above - i.e. this JSON is ignored.
 
-Let's see how that's done by looking at the console log.
+Let's see how that's happens by looking at the console log.
 
 ## Console log
 
@@ -192,7 +192,7 @@ Asset balance going into returned object:  1
 
 This below is already the auth stuff. This address format shown here is Polkadot but that doesn't matter (see further below) as our checks are already done against xx Chain.
 
-```json
+```raw
 token {
   name: 'the-dude',
   sub: '5GxeeFALkRvjnNgkiMjiP6q2GGnZ1ZmFyjCusHG4VoezqZSN',
@@ -229,12 +229,11 @@ You can configure the wallet to default to xx Network, by the way (see the scree
 
 This may be xx Network-specific and may not work with other Substrate-based chains. You need to check if your chain supports Assets, and how. It seems Polkadot removed their Assets pallet and has them on a parachain, it appears.
 
-### Missing NEXT_PUBLIC_TOKEN_ASSET_CFG
+### Missing `NEXT_PUBLIC_TOKEN_ASSET_CFG` may cause errors
 
-As mentioned several times, this variable is shown and output in logs, as well as compared to the hard-coded assetID in the app, but gating doesn't use that file.
+As I've mentioned several times, this variable is shown and output in console logs, as well as compared to the hard-coded assetID in the app, but gating doesn't consider its contents.
 
 If you don't have at least some items (XX and and an asset), code may not work as expected because the variable will be an empty JSON file (`{}`) which may cause errors. 
-
 Since the existence of that variable doesn't impact token or asset checks, you may as well leave it. Or remove it if you wish, as long as you can fix any errors that causes.
 
 ## License