Fix: more fixes

Author: lwasser

tutorials/publish-pypi.md

@@ -302,9 +302,12 @@ dist/pyospackage-0.1.0.tar.gz ... already exists
 
 ```
 
-If your credentials are valid, Hatch will publish your package to test PyPI.
+If your credentials are valid, and you have already run `hatch build`
+and thus have your 2 distribution files in a `dist/` directory then
+Hatch will publish your package to test PyPI.
 
-Hatch also has a caching system so once you enter your credentials it will remember them.
+Hatch also has a caching system so once you enter your credentials it
+will remember them.
 
 ## Install your package from test PyPI
 
@@ -319,7 +322,9 @@ This is an example landing page for the pyosPackage that was just uploaded. Noti
 :::
 
 
-As an example, [check out our pyOpenSci pyosPackage landing page on test PyPI](https://test.pypi.org/project/pyosPackage/). Notice the page has information about the current package version and also installation instructions as follows:
+As an example, [check out our pyOpenSci pyosPackage landing page on test PyPI](https://test.pypi.org/project/pyosPackage/). Notice that
+the page has information about the current package version and also
+installation instructions as follows:
 
 `pip install -i https://test.pypi.org/simple/ pyosPackage`
 
@@ -384,8 +389,7 @@ To do this:
 2. Click on the manage button for the project that you wish to add a token for
 3. Go to settings
 4. Click on "Create a token for your-package-name-here"
-5. Create the token and follow the steps above to open up the `.pypirc` file
-6. Replace the old account wide token with your new package token.
+5. Create the token and follow the steps above publish your package using the repository specific token.
 
 And you're all done!