fix: broken link

Author: lwasser

package-structure-code/pyproject-toml-python-package-metadata.md

@@ -5,8 +5,6 @@
 
 what's missing
 
-- missing explanation of `requires-python =` in this page -- discussed in slack with pradyun --
-
 ::: -->
 
 :::{admonition} Important pyproject.toml take aways
@@ -21,7 +19,6 @@ what's missing
 
 :::
 
-
 :::::{todo}
 
 when these are published, remove this todo
@@ -184,10 +181,9 @@ The examples at the bottom of this page contain ...
 
 - **`[project.scripts]` (Entry points):** Entry points are optional. If you have a command line tool that runs a specific script hosted in your package, you may include an entry point to call that script directly at the command line (rather than at the Python shell).
 
-  - Here is an example of[ a package that has entry point script](https://github.com/pyOpenSci/update-web-metadata/blob/main/pyproject.toml#L60)s. Notice that there are several core scripts defined in that package that perform sets of tasks. The pyOpenSci is using those scripts to process their metadata.
+  - Here is an example of[a package that has entry point script](https://github.com/pyOpenSci/pyosMeta/blob/main/pyproject.toml#L60)s. Notice that there are several core scripts defined in that package that perform sets of tasks. The pyOpenSci is using those scripts to process their metadata.
 - **Dynamic Fields:** if you have fields that are dynamically populated. One example of this is if you are using scm / version control based version with tools like `setuptooms_scm`, then you might use the dynamic field, such as version (using scm) **dynamic = ["version"]**
 
-
 ## Add dependencies to your pyproject.toml file
 
 The pyproject.toml file can also be used as a replacement for the requirements.txt file which has been traditionally used to store development dependencies such as pytest, code formatters such as Black and documentation tools such as sphinx.