Update tests/README.md

Co-authored-by: Lucas Hardt <Luc1412.lh@gmail.com>

Author: trevorflahardy

tests/README.md

@@ -35,12 +35,12 @@ Thus, all tests that make API calls will import and use the `ClientHybrid`.
 
 As an example, consider the user requesting to call `fetch_aes()` using the `ClientHybrid`:
 
-- The `ClientHybrid` class is initialized as a context manager, the same as you would with a `Client`.
-- The `fetch_aes()` method is called on the `ClientHybrid`.
-- The sync method of `fetch_aes()` is called on an internally held `SyncClient` class.
-- The async method of `fetch_aes()` is called on the `Client` itself.
-- The result, if reconstructable or comparable, is checked to ensure that both returned objects are the same.
-- The result of the async method call is returned as the final value.
+1. The `ClientHybrid` class is initialized as a context manager, the same as you would with a `Client`.
+2. The `fetch_aes()` method is called on the `ClientHybrid`.
+3. The sync method of `fetch_aes()` is called on an internally held `SyncClient` class.
+4. The async method of `fetch_aes()` is called on the `Client` itself.
+5. The result, if reconstructable or comparable, is checked to ensure that both returned objects are the same.
+6. The result of the async method call is returned as the final value.
 
 This approach, although loop blocking in nature, ensures that the results from both the `Client` and `SyncClient` are the same.