Fix: more edits

Author: lwasser

tutorials/publish-pypi.md

@@ -66,15 +66,17 @@ to practice and learn.
 
 ## 4 Steps for publishing a Python package on PyPI
 
-There are 4 things that you need to do to publish your Python package
+In this lesson you will learn how to publish your package to PyPI
+using [Hatch](https://hatch.pypa.io/latest/). There are 4 things that
+you need to do to publish your Python package:
 to PyPI. You need to:
 
-1. **Create a package development environment.** You will do this using Hatch.
-1. [**Build your package**](../package-structure-code/python-package-distribution-files-sdist-wheel). Building a package is the process of turning your code into 2 types of distribution files: sdist and wheel. The wheel distribution file is particularly important for users who will `pip install` your package.
+1. **Create a package development environment**
+1. [**Build your package using `hatch build`**](../package-structure-code/python-package-distribution-files-sdist-wheel). Building a package is the process of turning your code into 2 types of distribution files: sdist and wheel. The wheel distribution file is particularly important for users who will `pip install` your package.
 1. **Create an account on (test) PyPI**: You will need to create a PyPI account and associated token which provides permissions for you to upload your package.
-1. **Publish to PyPI using `hatch publish`**: Once you have completed the above two steps, you are ready to use `hatch` to publish your package!
+1. **Publish to PyPI using `hatch publish`**
+
 
-In this lesson you will learn how to publish your package to PyPI using [Hatch](https://hatch.pypa.io/latest/).
 In a future lesson, you will learn how to create an automated
 GitHub action workflow that publishes an updated
 version of your package to PyPI every time you create a GitHub release.
@@ -121,7 +123,7 @@ Hatch environment, it will automatically install your package into the environme
 source "/Path/to/env/here/hatch/env/virtual/pyosPackage/Mk7F5Y0T/sphinx-2i2c-theme/bin/activate"
 ```
 
-View what's in the environment:
+View what's in the environment using `pip list`:
 
 ```bash
 ➜ pip list
@@ -140,19 +142,31 @@ tzdata          2023.4
 
 At any time you can exit the environment using `exit`.
 
+```bash
+➜ hatch shell
+source "/Users/leahawasser/Library/Application Support/hatch/env/virtual/pyospackage/twO2iQR3/pyospackage/bin/activate"
+
+# Notice here you're in the (pyospackage) environment which is the default
+pyosPackage (☊ main) [✎ ×1 ] is 📦 v0.1.4 via 🐍 pyenv (pyospackage)
+➜ exit
+
+pyosPackage (☊ main) [✎ ×1 ] is 📦 v0.1.4 via 🐍 pyenv took 43s
+➜
+```
+
 
 ### Hatch and environments
 
 Behind the scenes when hatch creates a new virtual environment,
-by default it uses venv[^venv].
+by default it uses venv[^venv] which is the default environment management tool that comes with Python installations.
 
-hatch will:
-1. Create a new virtualenv (venv) that is located on your computer. You can customize the location of this environment if you wish  ....<where??>
+Hatch will:
+1. Create a new virtualenv (venv) that is located on your computer.
 2. Install your package into the environment in editable mode (similar to `pip install -e`). This means it installs both your project and your project's dependencies as declared in your pyproject.toml file.
 
 ## Step 2: Build your package's sdist and wheel distributions
 
-Once you have your development environment setup, you are ready to build your package using Hatch. Remember that building is the process of turning your Python package files into two distribution files:
+Once you have your development environment setup, you are ready to build your package using Hatch. Remember that building is the process of turning your Python package file structure into two distribution files:
 
 1. The [wheel distribution](#python-wheel) is a pre-built version of your package. It useful for users as it can be directly installed using a tool such as `pip`. This file has the extension `.whl`.
 2. The [source distribution](#python-source-distribution) is the files that make up your package in an unbuilt format. This file will have the extension `.tar.gz`.
@@ -161,7 +175,7 @@ You will use Hatch as a **Front end** tool that builds
 your package's sdist and wheel using the [hatchling](https://hatch.pypa.io/latest/) build back-end.
 The hatchling build back-end is used because you declared it in your pyproject.toml file in the [previous lesson](1-installable-code).
 
-To build your package run:
+To build your package run `hatch build`:
 
 ```bash
 ➜ hatch build
@@ -194,17 +208,17 @@ dist/pyospackage-0.1.0-py3-none-any.whl
 ### <i class="fa-solid fa-wand-magic-sparkles"></i> Congratulations - you've created your Python package distribution files <i class="fa-solid fa-wand-magic-sparkles"></i>
 
 You've now built your Python package and created your package distribution files. The next step is to setup
-your account on PyPI so you can publish your package.
+your account on testPyPI so you can publish your package.
 
 ## Step 3. Setup your test PyPI account
 
-Next, you'll setup an account on test PyPI. Remember that you
-are using test PyPI here instead of the real PyPI as a way to
+Next, you'll setup an account on Test PyPI. Remember that you
+are using test PyPI here instead of the PyPI as a way to
 safely learn how to publish a package without stressing the
 real PyPI's servers.
 
-:::{admonition} Test vs. real PyPI
-If you have a package that you are confident belongs on the real PyPI, all of the steps below will also work for you if you replace test.pypi.org with pypi.org wherever it appears.
+:::{admonition} Test PyPI vs. PyPI
+If you have a package that you are confident belongs on PyPI, all of the steps below will also work for you. When you publish using Hatch, you will call `hatch publish` to publish directly to PyPI instead of `hatch publish -r test` which publishes to Test PyPI.
 :::
 
 1. [Open up a web browser and go to the test PyPI website](https://test.pypi.org/).
@@ -236,7 +250,8 @@ use a backup device that only you can access to validate that the person logging
 
 This matters on PyPI because someone could login to your account and upload a version of your package that has security issues. These issues will then impact all of your users when they download and install that version of the package.
 
-2-factor authentication is now required for authentication on PyPI.
+2-factor authentication is required for PyPI authentication
+as of 1 January 2024.
 :::
 
 ## Step 4. Create a package upload token
@@ -260,24 +275,23 @@ It's ideal to create a package-specific token. When you create an account wide t
 * When you create your token, be sure to copy the token value and store it in a secure place before closing that browser.
 
 
+Your token should look something like this:
+
+`pypi-abunchofrandomcharactershere...`
 
+It should start with `pypi` followed by a dash and a bunch of characters.
 
 ### Upload to PyPI using Hatch
 
-Once you have the token in a safe place, you are ready to publish to
+Once you have your token, you are ready to publish to
 PyPI.
 
+* Run `hatch publish -r test`
 
-Your token should look something like this:
-
-`pypi-abunchofrandomcharactershere...`
-
-1. Finally run `hatch publish -r test`
-
--r stands for repository. In this case because you are publishing to test-PyPI you will use `-r test`. Hatch will then ask for a username and credentials.
+`-r` stands for repository. In this case because you are publishing to test-PyPI you will use `-r test`. Hatch will then ask for a username and credentials.
 
-* Add the word `__token__` for your username.
-* Paste your PyPI token value in for the credential values.
+* Add the word `__token__` for your username. This tells Test PyPI that you are using a token value rather than a username.
+* Paste your PyPI token value in at the `Enter your credentials` prompt:
 
 ```bash
 ❯ hatch publish -r test