Update geps/gep-2627/index.md

Co-authored-by: Candace Holman <[email protected]>

Author: maleck13

geps/gep-2627/index.md

@@ -9,7 +9,7 @@ For gateway infrastructure to be valuable we need to be able to connect clients
 
 ## Goals
 * Allow cluster operators or infrastructure providers to declaratively express which DNS service they want to use with a particular Gateway or Gateway Listener and have that DNS service interacted with via a controller to provision and configure the defined listener hostnames as DNS names and records based on the addresses assigned to the gateway instances.
-* Provide a standard CRD based API to provide an alternative to the need for "loose" APIs such as annotations that are not easily extended, standardized, versioned, or communicated about via a dedicated status. 
+* Provide a standard CRD-based API as an alternative to the need for "loose" APIs such as annotations.   Support an easily extended, standardized, versioned, and status-reporting API. 
 * Increase portability and supportability across gateway providers and third party implementors, for this type of key configuration
 
 ## Non-Goals