diff --git a/rfcs/0000-rfc-process.md b/rfcs/0000-rfc-process.md
index 58e55a4..231cc82 100644
--- a/rfcs/0000-rfc-process.md
+++ b/rfcs/0000-rfc-process.md
@@ -88,14 +88,19 @@ rubber stamp, and in particular still does not mean the feature will
 ultimately be merged; it does mean that in principle all the major
 stakeholders have agreed to the feature and are amenable to merging it.
 
-### Role of the "co-author"
+## Role of the "co-author"
 
-To goal for assigning a "co-author" to the RFC is multifold. The main
-responsability is to make themselves available for to the author to move the RFC
-along. It means keep a closer connection with them, talk and help resolve
-ongoing issues and add credence to the proposal. The co-author doesn't necessarily
-have to agree with all the points of the RFC but should generally be satisfied
-that the proposed additions are a good thing for the community.
+To goal for assigning a "co-author" is to help move the RFC along.
+
+The co-author should:
+* be available for discussion with the main author
+* respond to inquiries in a timely manner
+* help with fixing minor issues like typos so community discussion can stay
+  on design issues
+
+The co-author doesn't necessarily have to agree with all the points of the RFC
+but should generally be satisfied that the proposed additions are a good thing
+for the community.
 
 # Drawbacks
 [drawbacks]: #drawbacks