README: tweaks

README.md

@@ -181,8 +181,9 @@ make test-kubo-subdomains
 
 If you are using a different gateway and would like to use a different configuration, the [Makefile](./Makefile) and configuration scripts are great, up-to-date, starting points.
 
-The test-suite is a regular go test-suite, which means that any IDE integration will work as-well.
-You can use env variables to configure the tests from your IDE.
+> [!NOTE]
+> The test-suite is a regular go test-suite, which means that any IDE integration will work as-well.
+> You can use env variables to configure the tests from your IDE.
 
 Here is an example for VSCode, `example.com` is the domain configured via [kubo-config.example.sh](./kubo-config.example.sh)
 
@@ -317,4 +318,4 @@ Please let us know if you would like to see this feature implemented directly in
 - How to deal with subdomains & configuration (t0114 for example)?
   - Some test relies on querying URLs like `http://$CIDv1.ipfs.example.com/`. While `http://$CIDv1.ipfs.localhost/` works by default, do we need / want to test with `.example.com`?
 - Debug logging
-  - Set the environment variable `GOLOG_LOG_LEVEL="conformance=debug"` to toggle debug logging.
+  - Set the environment variable `GOLOG_LOG_LEVEL="conformance=debug"` to toggle debug logging.