Fix: add note about publishing to test pypi & link fix

Fix: bad link

Fix: add 429 http code

Author: lwasser

.github/workflows/build-book.yml

@@ -68,4 +68,4 @@ jobs:
         directory: '_build/html'
         arguments: |
           --ignore-files "/.+\/_static\/.+/,/genindex.html/"
-          --ignore-status-codes "404, 403, 503"
+          --ignore-status-codes "404, 403, 429, 503"

documentation/repository-files/license-files.md

@@ -37,7 +37,7 @@ Licenses are legally binding, as such you should avoid trying to create your own
 
 ### Use open permissive licenses when possible
 
-We generally suggest that you use a permissive, license that is [Open Software Initiative (OSI) approved](https://opensource.org/licenses). If you are
+We generally suggest that you use a permissive, license that is [Open Software Initiative (OSI) approved](https://opensource.org/licenses/). If you are
 [submitting your package to pyOpenSci for peer review](https://www.pyopensci.org/about-peer-review/index.html), then we require an OSI approved
 license.
 

tutorials/publish-pypi.md

@@ -328,6 +328,11 @@ installation instructions as follows:
 
 `pip install -i https://test.pypi.org/simple/ pyosPackage`
 
+:::{important} Publishing to test.PyPI.org vs PyPI.org
+While you can install from test PyPI it's not recommended that you publish to
+testPyPI as a permanent way to install your package. Test PyPi is a perfect place to learn how to publish your package. But your end goal should be to publish to PyPI.org once you have figured out your workflow.
+:::
+
 ### Time to install your package
 
 * On your computer, activate the development environment that