uhoreg fixes my spelling

Co-authored-by: Hubert Chathi <hubert@uhoreg.ca>

proposals/2666-get-rooms-in-common.md

@@ -11,7 +11,7 @@ invites on their own do not present much context. With this endpoint, a client c
 rooms you have in common before you accept an invite.
 
 While this information can be determined if the user has full access to member state for all rooms,
-modern clients often implement "lazy-loadeding", so they often only have state for a subset of all rooms
+modern clients often implement "lazy-loading", so they often only have a subset of state for the rooms
 the user is in. Therefore, the homeserver should have a means to provide this information.
 
 This proposal aims to implement a simple mechanism to fetch rooms you have in common with another user.
@@ -19,7 +19,7 @@ This proposal aims to implement a simple mechanism to fetch rooms you have in co
 ## Proposal
 
 Homeservers should implement a new endpoint `/users/{current_user}/shared_rooms/{other_user_id}` which will take
-the authenticated users MxID and the user that is being searched for.
+the authenticated user's MxID and the user that is being searched for.
 
 The response format will be an array containing all rooms where both the `current_user` and `other_user_id` have
 a membership of type `join`. If either user is not joined to any rooms, or the `other_user_id` does not exist, an