Fix broken links

Author: awgreene

content/en/docs/Concepts/crds/CatalogSource.md

@@ -5,7 +5,7 @@ weight: 3
 
 A CatalogSource represents a store of metadata that OLM can query to discover and install operators and their dependencies.
 
-The `.spec` of a CatalogSource indicates to how to construct a pod or how to talk to a service that serves the [operator-registry grpc api](/docs/concepts/olm-architecture/operator-registry/using-catalog-locally). 
+The `.spec` of a CatalogSource indicates to how to construct a pod or how to talk to a service that serves the [operator-registry grpc api](/docs/concepts/olm-architecture/operator-registry/using-a-catalog-locally). 
 
 There are three primary types:
 

content/en/docs/Concepts/olm-architecture/operator-registry/building-a-catalog.md

@@ -79,7 +79,7 @@ For more detail on using `opm` to generate index images, take a look at the [doc
 <pre></pre>
 ## Where should I go next?
 
-* [Use the catalog of operators locally](/docs/concepts/olm-architecture/operator-registry/using-catalog-locally/): Test your catalog locally 
-* [Using a Catalog with OLM](/docs/concepts/olm-architecture/operator-registry/using-catalog-with-olm/): Make your operator available for OLM in a cluster
+* [Use the catalog of operators locally](/docs/concepts/olm-architecture/operator-registry/using-a-catalog-locally): Test your catalog locally 
+* [Using a Catalog with OLM](/docs/concepts/olm-architecture/operator-registry/using-catalog-with-olm): Make your operator available for OLM in a cluster