Final tweaks to Python packaging lecture

Author: IshaanDesai

03_building_and_packaging/intro_slides.md

@@ -27,7 +27,7 @@ slideOptions:
 
 ---
 
-## Learning goals of chapter
+## Learning Goals of Chapter
 
 - Explain why software is packaged.
 - Create a distributable package of a Python code, publish on PyPI, and install with pip.
@@ -38,7 +38,7 @@ slideOptions:
 
 ---
 
-## What is packaging?
+## What is Packaging?
 
 - Bare code is often hard to understand for everyone except the developer(s).
 - Packaging is a workflow to convert a code into a standardized distributable software.
@@ -50,7 +50,7 @@ slideOptions:
 
 ---
 
-## Why should we package code? 1/2
+## Why Package Code? 1/2
 
 - A code with many files typically has difficulties like
     - multiple dependencies and requirements of specific versions of dependencies.
@@ -59,7 +59,7 @@ slideOptions:
 
 ---
 
-## Why should we package code? 2/2
+## Why Package Code? 2/2
 
 - Create a package to
     - benefit from a package index or package manager which is familiar to a broad audience.
@@ -69,7 +69,7 @@ slideOptions:
 
 ---
 
-## How to package code?
+## How to Package Code?
 
 - First step is finding the right standard for your code.
 - There are several options:
@@ -83,15 +83,15 @@ slideOptions:
 
 ---
 
-## Why do we look at packaging a Python code?
+## Why Packaging a Python Code?
 
 - Python is easy to understand and widely used in research software.
 - Well established package managers and packaging tools already exist in the Python community.
-- Several examples of packaged codes: [NumPy](https://pypi.org/project/numpy/), [SciPy](https://pypi.org/project/scipy/), [PyTorch](https://pypi.org/project/torch/).
+- Many famous examples: [NumPy](https://pypi.org/project/numpy/), [SciPy](https://pypi.org/project/scipy/), [PyTorch](https://pypi.org/project/torch/).
 
 ---
 
-## Key takeaways
+## Key Takeaways
 
 - Packaging or creating build recipe of a code is a standardized process.
 - Many options in packaging / building tools.

03_building_and_packaging/pypi_slides.md

@@ -64,8 +64,8 @@ In this lecture we work with pip, because ...
 
 ## Python Enhancement Proposals (PEPs)
 
-- PEP is an evolving design document which guides Python development.
-- PEPs typically involve concise technical information, which also act as standards.
+- PEPs are evolving design documents that guide Python development.
+- PEPs typically involve concise technical information. They are essentially standards.
 - Packaging is standardized by [Packaging PEPs](https://peps.python.org/topic/packaging/).
 - Example of a Packaging PEP: [PEP 427 – The Wheel Binary Package Format 1.0](https://peps.python.org/pep-0427/).
 
@@ -84,13 +84,13 @@ Import package ...
 - ... is used within a file: `import pkg` or `from pkg import xyz`.
 - ... is available when its distribution package is installed.
 
-Distribution package name and import package need not be the same, but usually is. Read more about [distribution package vs. import package](https://packaging.python.org/en/latest/discussions/distribution-package-vs-import-package/#distribution-package-vs-import-package).
+Both names need not be the same, but they usually are. Read more about [distribution package vs. import package](https://packaging.python.org/en/latest/discussions/distribution-package-vs-import-package/#distribution-package-vs-import-package).
 
 ---
 
 ## Steps in Packaging a Python Code
 
-1. Get or create a source tree of the code.
+1. Create a source tree of the code.
 2. Write a packaging configuration file, typically `pyproject.toml`.
 3. Create build artifacts.
 4. Upload the build artifacts to a packaging index.
@@ -203,7 +203,7 @@ python3 -m build
 
 Source distribution (sdist)
 
-- Contains files enough to install the package from source.
+- Contains files to install the package from source.
 - Run
 
   ```bash
@@ -216,7 +216,7 @@ Source distribution (sdist)
 
 Built distribution (wheel)
 
-- Contains files needed only to run package.
+- Contains binary files to run package.
 - No compilation done, just a copy paste into a directory.
 - In most cases only one generic wheel is required. Exceptions are different Python interpreters, different OS configurations.
 - Run