Minor fix on #09

MAINTAINERS.md

@@ -6,7 +6,7 @@ This guide is intended for maintainers — anybody with commit access to one or
 
 A master branch. This branch MUST be releasable at all times. Commits and merges against this branch MUST contain only bugfixes and/or security fixes. Maintenance releases are tagged against master.
 
-A develop branch. This branch contains your proposed changes,
+A develop branch. This branch contains your proposed changes.
 
 The remainder of this document details how to merge pull requests to the repositories.
 
@@ -41,4 +41,4 @@ Does the issue contain narrative indicating the need for the feature? If not, as
 
 Are new unit tests in place that test all new behaviors introduced? If not, do not merge the feature until they are!
 Is documentation in place for the new feature? (See the documentation guidelines). If not do not merge the feature until it is!
-Is the feature necessary for general use cases? Try and keep the scope of any given component narrow. If a proposed feature does not fit that scope, recommend to the user that they maintain the feature on their own, and close the request. You may also recommend that they see if the feature gains traction amongst other users, and suggest they re-submit when they can show such support.
+Is the feature necessary for general use cases? Try and keep the scope of any given component narrow. If a proposed feature does not fit that scope, recommend to the user that they maintain the feature on their own, and close the request. You may also recommend that they see if the feature gains traction amongst other users, and suggest they re-submit when they can show such support.