A few corrections.

README.md

@@ -114,7 +114,7 @@ The following are the requirements to **start**.
 
 This project welcomes contributions and suggestions.  Most contributions require you to agree to a
 Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us
-the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
+the rights to use your contribution. For details, visit [Microsoft Open Source](https://cla.opensource.microsoft.com).
 
 When you submit a pull request, a CLA bot will automatically determine whether you need to provide
 a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions

cluster-management/README.md

@@ -33,4 +33,4 @@ Flux Operator
 
 Azure
 
-* [Azure ARC for Kubernetes - Coming Soon]()
+* [Azure ARC for Kubernetes](https://azure.microsoft.com/en-us/resources/videos/kubernetes-app-management-with-azure-arc/)

observability/README.md

@@ -20,7 +20,7 @@ Your third challenge is to detect when **Pods Restart**. Similar to Nodes Not Re
 
 ### Infrastructure Monitoring #4
 
-Your fourth challenge is to detect when **Deployments are Not Ready**. This is simlar to Pods restarting, but how do you detect a workload deployment problem if the Pod does not even startup? Typical problems in this area are Pods not able to be scheduled due to Cluster resource capacity or a desired Node not found. 
+Your fourth challenge is to detect when **Deployments are Not Ready**. This is simlar to Pods restarting, but how do you detect a workload deployment problem if the Pod does not even startup? Typical problems in this area are Pods not able to be scheduled due to Cluster resource capacity or a desired Node not found.
 
 ## Success Criteria