fix readme (#4)

README.md

@@ -22,7 +22,7 @@ We welcome [issues](https://github.com/GovStackWorkingGroup/test-utils/issues) t
 1. Merge pull requests with desired changes to the main branch.
     - For the best experience, squash-and-merge and use [Conventional Commit Messages](https://conventionalcommits.org/).
 2. Find the current version of the orb.
-    - You can run `circleci orb info GovStackWorkingGroup/testutils | grep "Latest"` to see the current version.
+    - You can run `circleci orb info govstack-working-group/testutils | grep "Latest"` to see the current version.
 3. Create a [new Release](https://github.com/GovStackWorkingGroup/test-utils/releases/new) on GitHub.
     - Click "Choose a tag" and _create_ a new [semantically versioned](http://semver.org/) tag. (ex: v1.0.0)
       - We will have an opportunity to change this before we publish if needed after the next step.
@@ -31,4 +31,4 @@ We welcome [issues](https://github.com/GovStackWorkingGroup/test-utils/issues) t
     - If you have used _[Conventional Commit Messages](https://conventionalcommits.org/)_ it will be easy to determine what types of changes were made, allowing you to ensure the correct version tag is being published.
 5. Now ensure the version tag selected is semantically accurate based on the changes included.
 6. Click _"Publish Release"_.
-    - This will push a new tag and trigger your publishing pipeline on CircleCI.
+    - This will push a new tag and trigger your publishing pipeline on CircleCI.