Apply suggestions from code review

Co-authored-by: viktoriaas <[email protected]>
Co-authored-by: Antonio Ojea <[email protected]>

Author: 3 people

sigs.yaml

@@ -3620,6 +3620,9 @@ workinggroups:
   contact:
     slack: wg-checkpoint-restore
     mailing_list: https://groups.google.com/forum/#!forum/kubernetes-wg-checkpoint-restore
+    liaison:
+      github: BenTheElder
+      name: Benjamin Elder
 - dir: wg-data-protection
   name: Data Protection
   mission_statement: >

wg-checkpoint-restore/README.md

@@ -33,6 +33,7 @@ The [charter](charter.md) defines the scope and governance of the Checkpoint Res
 - Slack: [#wg-checkpoint-restore](https://kubernetes.slack.com/messages/wg-checkpoint-restore)
 - [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-wg-checkpoint-restore)
 - [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/wg%2Fcheckpoint-restore)
+- Steering Committee Liaison: Benjamin Elder (**[@BenTheElder](https://github.com/BenTheElder)**)
 <!-- BEGIN CUSTOM CONTENT -->
 
 <!-- END CUSTOM CONTENT -->

wg-checkpoint-restore/charter.md

@@ -77,11 +77,9 @@ Additionally, the WG commits to:
 
 ## Timelines and Disbanding
 
-As a first mandate, the WG will define a roadmap and tasks in the first quarter
-of operation.
+As a first mandate, the WG will propose a draft roadmap and identify key tasks in the first quarter of operation.
 
-After that the WG will distribute the different tasks to different community
-members to define possible APIs and how it can be integrated in Kubernetes.
+After that, the WG will facilitate collaboration among community members to explore possible APIs and draft proposals for their integration into Kubernetes, which will then be presented to the relevant SIGs.
 
 Achieving the aforementioned deliverables, also mentioned in the `In Scope`
 section, will allow us to decide when to disband this WG.  There is no