Update src/feature-lifecycle/summary.md

Co-authored-by: Ben Kimock <[email protected]>

Author: Amanieu

src/feature-lifecycle/summary.md

@@ -29,7 +29,7 @@ Once a feature is deemed suitable for inclusion in the standard library, the exa
 
 Keep the following points in mind during the discussion:
 - Resist the temptation to make the API overly general since this tends to increase complexity and lowers the chance of it being accepted by the library team. Instead, try to stay focused on the problem that needs solving.
-- An alternative that should *always* be considered is simply adding this feature via a third party crate. This even possible when adding new methods to standard library types by using extension traits.
+- An alternative that should *always* be considered is simply adding this feature via a third party crate. This is even possible when adding new methods to standard library types by using extension traits.
 - In the case of "convenience" functions which are simply shorthands for something that is already possible with existing APIs, the cost of extending the standard library surface should be weighed against the ergonomic impact of the new functions.
 
 The library team itself is not directly involved in this discussion, but individual members may comment to provide feedback.