Update annual-report-2021.md

Add some input from the others.

1 files changed, 18 insertions, 6 deletions

diff --git a/sig-docs/annual-report-2021.md b/sig-docs/annual-report-2021.md
index 8301bd70..a46d2ffd 100644
--- a/sig-docs/annual-report-2021.md
+++ b/sig-docs/annual-report-2021.md
@@ -29,6 +29,10 @@ Tim Bannister ([sftim](https://github.com/sftim))
     
     Quite small (usually 5-10 people) and generally we try to make people feel comfortable to give their opinion.
     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,
+    tips, or toolings that may be can be reused by other team as well.
 
 
 **How does the group get updates, reports, or feedback from subprojects? Are there any springing up or being retired?
@@ -58,11 +62,9 @@ We don't have an official way of measuring membership.
 **How does the group measure reviewer and approver bandwidth? Do you need help in any area now? What are you doing about it?**
 
 PR are generally open for anyone to review. We have [PR wrangler rotation](https://github.com/kubernetes/website/wiki/PR-Wranglers).
-In general each of the approver will taking the rotation. Under exceptional circumstances where there's lots of
-pressure for the wrangler, another approver usually will be willing to help.
+In general each of the approver will taking the rotation. Each approver participates in the PR wrangler rotation. Approvers are supported during their rotation by other reviewers and approvers.
 
-For technical reviews, other than SIG Docs Tech Leads, we also notify respective SIGs with necessary knowledge of the
-technical aspect of the content.
+For technical reviews, other than SIG Docs Tech Leads, we also notify respective SIGs with necessary knowledge of the technical aspect of the content. SIG Docs receives contributions from community members representing different SIGs. During the PR review process, SIG Docs reaches out to other SIGs when a pull request requires technical review.
 
 **Is there a healthy onboarding and growth path for contributors in your SIG? 
 What are some activities that the group does to encourage this? 
@@ -75,19 +77,29 @@ 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.
+
 **What programs do you participate in for new contributors?**
 
 We have an in person session during the KubeCon.
 
 **Does the group have contributors from multiple companies/affiliations? 
+
+Yes
+
 Can end users/companies contribute in some way that they currently are not?**
 
-<!-- TODO -->
+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.
 
+Longer term projects include
+
+- co-ordination 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?**
 
@@ -101,7 +113,7 @@ We have ongoing KEP, but we don't have a deadline set on when it should be finis
 
 **What areas and/or subprojects does the group need the most help with?**
 
-<!-- TODO -->
+- Blog subproject
 
 **What's the average open days of a PR and Issue in your group? / what metrics does your group care about and/or measure?**