sharing: Fix typos

rfc/src/sharing.xml

@@ -207,7 +207,7 @@ for this Principal that the user has access to, or null if none.</t></li>
 <li><t><strong>newRights</strong>: <tt>String[Boolean]|null</tt> (immutable; server-set)</t>
 <t>The "myRights" property of the object for the user after the change.</t></li>
 <li><t><strong>name</strong>: <tt>String</tt> (immutable; server-set)</t>
-<t>The name of the object at the time the notification was made. Determining the name will depend on the data type in question. For example it might be the "title" property of a CalendarEvent or the "name" of a Mailbox. The name is to show to users who have had their access rights to the object removed, so that these users know what it is they can no longer access.</t></li>
+<t>The name of the object at the time the notification was made. Determining the name will depend on the data type in question. For example, it might be the "title" property of a CalendarEvent or the "name" of a Mailbox. The name is to show to users who have had their access rights to the object removed, so that these users know what it is they can no longer access.</t></li>
 </ul>
 </section>
 
@@ -268,7 +268,7 @@ for this Principal that the user has access to, or null if none.</t></li>
 </ul>
 
 <section anchor="example"><name>Example</name>
-<t>Suppose we are designing a data model for a very simple todo list. There is a Todo data type representing a single item to do, each of which belongs to a single TodoList. The specification makes the lists sharable by referencing this document and defining the common properties.</t>
+<t>Suppose we are designing a data model for a very simple todo list. There is a Todo data type representing a single item to do, each of which belongs to a single TodoList. The specification makes the lists shareable by referencing this document and defining the common properties.</t>
 
 <t>First it would define a set of domain-specific rights. For example, a TodoListRights object may have the following properties:</t>