Apply suggestions from code review

Co-authored-by: Jim Angel <jimangel@users.noreply.github.com>

1 files changed, 15 insertions, 9 deletions

diff --git a/sig-docs/annual-report-2021.md b/sig-docs/annual-report-2021.md
index a46d2ffd..a4c29c23 100644
--- a/sig-docs/annual-report-2021.md
+++ b/sig-docs/annual-report-2021.md
@@ -31,7 +31,7 @@ Tim Bannister ([sftim](https://github.com/sftim))
     Meeting notes are up to date. We have recording of the meetings uploaded.
     
     We have a new sub-project, it's localization sub-project, where we conduct monthly meeting 
-    attended by all people from the localizatiin team. This sub-porjcet focusing on sharing any concerns,
+    attended by all people from the localization team. This sub-project focusing on sharing any concerns,
     tips, or toolings that may be can be reused by other team as well.
 
 
@@ -47,7 +47,7 @@ Yes it is.
 
 **When was your last monthly community-wide update? (provide link to deck and/or recording)**
 
-<!-- TODO -->
+[Q2 of 2020 (created April 8 2020)](https://docs.google.com/presentation/d/12WnYz8SbjWRZbK4k2qlc1Ab7Z-f2F7kk-Tb2eRTfTy8/edit?usp=sharing).
 
 ## Membership
 
@@ -77,39 +77,42 @@ contributors. There are issues labelled for the different contribution areas (we
 blog, first time contributors, task, concept, API, etc) which helps new contributors 
 identify how to get started.
 
-From time to time we use the weekly meeting Zoom call to help new contributors get onboard.
+From time to time we use the weekly meeting Zoom calls to help new contributors get onboard.
 
 **What programs do you participate in for new contributors?**
 
-We have an in person session during the KubeCon.
+We used to host doc sprints during the KubeCon,
+the doc sprints acted as a way to onboard new contributors as well as tackle a lot of open issues.
 
-**Does the group have contributors from multiple companies/affiliations? 
+**Does the group have contributors from multiple companies/affiliations?**
 
 Yes
 
-Can end users/companies contribute in some way that they currently are not?**
+**Can end users/companies contribute in some way that they currently are not?**
 
 I suppose we're particular keen to hear about suggested improvements from people who are using Kubernetes in production and can see gaps in what's there.
 
 ## Current initiatives and project health
 
-[ ] Please include links to KEPs and other supporting information that will be beneficial to multiple types of community members.
+- [x] Please include links to KEPs and other supporting information that will be beneficial to multiple types of community members.
 
 Longer term projects include
 
-- co-ordination with WG naming for things like removing the word “slave” (and other problematic terms) from docs.
+- coordination with WG naming for things like removing the word “slave” (and other problematic terms) from docs.
 - publishing better information about releases kubernetes/website#20293
 
 **What are initiatives that should be highlighted, lauded, shout out, that your group is proud of? 
 Currently underway? What are some of the longer tail projects that your group is working on?**
 
-<!-- TODO -->
+Shoutout to docsy theme work as well as the reference documentation generation :tada:.
 
 **Year to date KEP work review: What’s now stable? Beta? Alpha? Road to alpha?**
 
 We have ongoing KEP, but we don't have a deadline set on when it should be finished.
 
 - [Doc policies for third party content](https://github.com/kubernetes/enhancements/tree/master/keps/sig-docs/1326-third-party-content-in-docs)
+  There's also an umbrella issue written as well [kubernetes/website#20232](https://github.com/kubernetes/website/issues/20232).
+
 
 **What areas and/or subprojects does the group need the most help with?**
 
@@ -123,3 +126,6 @@ We have the information from [devstat](https://k8s.devstats.cncf.io/d/25/open-pr
 
 For example, based on 10/01/2020 data, we have:
 Average number of opened PRs 1.23 K with the median opened PRs age 3 days 13 hours 52 minutes 10 seconds.
+In addition, we informally review metrics quarterly as well as ad hoc if anyone brings it up at a weekly meeting.
+We aim to have < 100 open PRs for the English localization,
+and will take steps as needed if we see the figure climbing much above that.