docs: polish wording and fix minor grammar (#785)

Author: sashaodessa

README.md

@@ -91,9 +91,9 @@ contract TestContract is Test {
         assertEq(test.exists(), 100);
     }
 
-    // It supports arbitrary storage layouts, like assembly based storage locations
+    // It supports arbitrary storage layouts, like assembly-based storage locations
     function testFindHidden() public {
-        // `hidden` is a random hash of a bytes, iteration through slots would
+        // `hidden` is a random hash of bytes; iterating through slots would
         // not find it. Our mechanism does
         // Also, you can use the selector instead of a string
         uint256 slot = stdstore.target(address(test)).sig(test.hidden.selector).find();
@@ -167,7 +167,7 @@ contract Storage {
 
 ### stdCheats
 
-This is a wrapper over miscellaneous cheatcodes that need wrappers to be more dev friendly. Currently there are only functions related to `prank`. In general, users may expect ETH to be put into an address on `prank`, but this is not the case for safety reasons. Explicitly this `hoax` function should only be used for addresses that have expected balances as it will get overwritten. If an address already has ETH, you should just use `prank`. If you want to change that balance explicitly, just use `deal`. If you want to do both, `hoax` is also right for you.
+This is a wrapper around miscellaneous cheatcodes that need wrappers to be more dev-friendly. Currently there are only functions related to `prank`. In general, users may expect ETH to be put into an address on `prank`, but this is not the case for safety reasons. Explicitly, this `hoax` function should only be used for addresses that have expected balances as it will get overwritten. If an address already has ETH, you should just use `prank`. If you want to change that balance explicitly, just use `deal`. If you want to do both, `hoax` is also right for you.
 
 #### Example usage:
 

RELEASE_CHECKLIST.md

@@ -8,5 +8,5 @@ This checklist is meant to be used as a guide for the `forge-std` release proces
 - [ ] Open and merge a PR with the version bump
 - [ ] Tag the merged commit with the version number: `git tag v<X.Y.Z>`
 - [ ] Push the tag to the repository: `git push --tags`
-- [ ] Create a new GitHub release with the automatically generated changelog and with the name set to `v<X.Y.Z>`
+- [ ] Create a new GitHub release with the automatically generated changelog and the name set to `v<X.Y.Z>`
 - [ ] Add `## Featured Changes` section to the top of the release notes