Merge pull request #367 from shubheksha/fix-broken-113-meeting-min-link

Fix broken link and some typos

releases/release-1.13/README.md

@@ -4,7 +4,7 @@
 
 * [This document](https://git.k8s.io/sig-release/releases/release-1.13/README.md)
 * [Release Team](https://git.k8s.io/sig-release/releases/release-1.13/release_team.md)
-* Zoom: join Google Group to receive meeting invite
+* Zoom: join [Google Group](https://groups.google.com/forum/#!forum/kubernetes-milestone-burndown) to receive meeting invite
 * [Slack](https://kubernetes.slack.com/messages/sig-release/)
 * [Forum](https://groups.google.com/forum/#!forum/kubernetes-sig-release)
 * [Enhancements Tracking Sheet](http://bit.ly/k8s113-enhancements)
@@ -119,7 +119,7 @@ This should occur before 1.13.0-beta.1 is cut so we have time to gather signal o
 
 ### Docs
 
-If an enhancement needs documentation, enter Yes in the enhancement tracking spreadsheet and add a link to the documentation PR. You can open documentation PRs in the [kubernetes/website](https://github.com/kubernetes/website) repository. If you have questions, the release documentation lead, or representatives from SIG-Docs will be happy to assist you.
+If an enhancement needs documentation, enter "Yes" in the enhancement tracking spreadsheet and add a link to the documentation PR. You can open documentation PRs in the [kubernetes/website](https://github.com/kubernetes/website) repository. If you have questions, the release documentation lead, or representatives from SIG-Docs will be happy to assist you.
 
 For documentation PRs:
 
@@ -128,7 +128,7 @@ For documentation PRs:
 
 ### Burndown
 
-Burndown meetings are held on Mondays, Wednesdays and Fridays at TIME TBD until the final release is near, and then every business day until the release.  These meetings may overlap with other SIG meetings and the Community Meeting, but it is critical that SIGs provide representation at the release burndown meeting when requested to discuss specific issues and insure they do not become gating on the release. The release lead or a release team representative will keep the Community Meeting informed of release status even if there are meeting conflicts.
+Burndown meetings are held on Mondays, Wednesdays and Fridays at 10am PST until the final release is near, and then every business day until the release. These meetings may overlap with other SIG meetings and the Community Meeting, but it is critical that SIGs provide representation at the release burndown meeting when requested to discuss specific issues and ensure they do not become gating on the release. The release lead or a release team representative will keep the Community Meeting informed of release status even if there are meeting conflicts.
 
 Join the [Kubernetes Milestone Burndown Group](https://groups.google.com/forum/#!forum/kubernetes-milestone-burndown) to get the calendar invite.
 
@@ -137,7 +137,7 @@ The intent of these meetings is to:
 * Focus on fixing bugs, eliminating test flakes and general release stabilization.
 * Ensure docs and release notes are written and accurate.
 * Identify all enhancement going into the release, and make sure alpha, beta, GA is marked in enhancements repo.
-* Provide a [one-stop view of release progress](http://bit.ly/kube113-minutes) including relevant release metrics.
+* Provide a [one-stop view of release progress](https://bit.ly/k8s113-minutes) including relevant release metrics.
 * Host SIG stakeholders for updates.
 
 [master-blocking]: https://testgrid.k8s.io/sig-release-master-blocking#Summary