Fix: multiple broken links (#187)

* Fix: multiple broken links

* Fix: better link

* Fix: one last conda link fix

Author: lwasser

package-structure-code/publish-python-package-pypi-conda.md

@@ -48,13 +48,13 @@ Click here for a tutorial on publishing your package to PyPI.
 :::
 
 
-```{tip}
+:::{tip}
 On the package build page, we discussed the [two package distribution
 types that you will create when making a Python package](python-package-distribution-files-sdist-wheel): SDist (packaged as a .tar.gz or .zip) and
 Wheel (.whl) which is really a zip file. Both of those file "bundles" will
 be published on PyPI when you use [a standard build tool](python-package-build-tools) to build
 your package.
-```
+:::
 
 (about-conda)=
 ## What is Anaconda Cloud and conda?
@@ -154,11 +154,11 @@ to use conda to manage their local environments (which many do), you should
 consider publishing to both PyPI and the conda-forge channel (_more
 on that below_).
 
-```{admonition} Additional resources
-* [learn more about why conda-forge was created, here](https://conda-forge.org/docs/user/introduction.html#why-conda-forge)
+:::{admonition} Additional resources
+* [learn more about why conda-forge was created, here](https://conda-forge.org/docs/user/introduction.html)
 
 * [To learn more about conda terminology, check out their glossary.](https://docs.conda.io/projects/conda/en/latest/glossary.html )
-```
+:::
 
 <!-- One of our packages on conda-forge https://anaconda.org/conda-forge/pandera -->
 
@@ -169,7 +169,7 @@ we encourage you to consider doing so!
 
 Once your package is on PyPI, the process to add your package to conda-forge
 is straight forward to do. [You can follow the detailed steps provided
-by the conda-forge maintainer team.](https://conda-forge.org/docs/maintainer/adding_pkgs.html#generating-the-recipe).
+by the conda-forge maintainer team.](https://conda-forge.org/docs/maintainer/adding_pkgs.html).
 
 
 :::{button-link} ../tutorials/publish-conda-forge.html
@@ -184,9 +184,9 @@ If you want a step by step tutorial, click here.
 
 Once your package is added, you will have a feedstock repository on GitHub with your packages name
 
-```{tip}
+:::{tip}
 [Here is an example conda-forge feedstock for the pyOpenSci approved package - movingpandas](https://github.com/conda-forge/movingpandas-feedstock)
-```
+:::
 
 ### Maintaining your conda-forge package repository
 

tutorials/add-readme.md

@@ -187,7 +187,6 @@ Short description here using non-technical language that describes what your pac
 
 ## How to install pyosPackage
 
-<todo - when i add more to the pyos package this can use that readme>
 To install this package run:
 
 `pip install pyosPackage`
@@ -223,7 +222,7 @@ above is a set of recommendations as you are just getting started. You may find
 the need for other elements to be added to this file as you further develop your
 package and as a community begins to use your package.
 
-In the [next lesson](add-license-coc), you will add a LICENSE file to
+In the [next lesson](add-license-coc.md), you will add a LICENSE file to
 your Python package. A license file is critical as it tells users
 how they legally can (and can't) use your package. It also:
 

tutorials/publish-conda-forge.md

@@ -403,7 +403,7 @@ build:
  number: 0
 ```
 
-> - [x] A tarball (`url`) rather than a repo (e.g. `git_url`) is used in your recipe (see [here](https://conda-forge.org/docs/maintainer/adding_pkgs.html#build-from-tarballs-not-repos) for more details).
+> - [x] A tarball (`url`) rather than a repo (e.g. `git_url`) is used in your recipe (see [here](https://conda-forge.org/docs/maintainer/adding_pkgs.html) for more details).
 
 **Translation:** Here conda wants you to provide a link to the source distribution on PyPI rather than a link to your GitHub repository distribution. Notice above in the Source section of your recipe there is a `url:` section that provides a PyPI url that ends in tar.gz. That is a link to your source distribution that conda-forge will use.