Update package-structure-code/complex-python-package-builds.md

Co-authored-by: Carol Willing <carolcode@willingconsulting.com>

package-structure-code/complex-python-package-builds.md

@@ -29,7 +29,7 @@ more information about front-end and back-end compatibility.
 In this packaging guide we recommend using `hatch` along with it's preferred back-end `hatchling`. One reason to use
 hatch with an alternate back-end is for creating an extension module. A Python extension module is one that is make up,
 either in part or entirely, of compiled code. In this case the back-end chosen (such as `meson-python`) must know how to
-compile the extension language and bind it to Python but `hatchling` is only capable of building pure Python modules.
+compile the extension language and bind it to Python since `hatchling` is only capable of building pure Python modules.
 
 In order to use a different back-end you will need to edit your project's `pyproject.toml`. If you have a
 `pyproject.toml` generated by the `hatch` command, or from following the packaging tutorial, you may have