EHR MAY call discovery endpoint

Fixes #212

Author: isaacvetter

docs/specification/1.0.md

@@ -25,7 +25,7 @@ CDS Hooks implementers are not required to use the Open API Specification interf
 
 ## Discovery
 
-Developers of CDS Services SHALL provide a stable endpoint for allowing EHRs to discover available CDS Services, including information such as the purpose of the CDS Service, when it should be invoked, and any data that is requested to be prefetched.
+Developers of CDS Services SHALL provide a stable endpoint for allowing EHRs to discover available CDS Services, including information such as the purpose of the CDS Service, when it should be invoked, and any data that is requested to be prefetched. 
 
 A CDS Service provider SHALL expose its Discovery endpoint at"
 
@@ -34,7 +34,7 @@ A CDS Service provider SHALL expose its Discovery endpoint at"
 ```
 ### HTTP Request
 
-The discovery endpoint SHALL always be available at `{baseUrl}/cds-services`. For example, if the `baseUrl` is https://example.com, the EHR would invoke:
+The discovery endpoint SHALL always be available at `{baseUrl}/cds-services`. For example, if the `baseUrl` is https://example.com, the EHR MAY invoke:
 
 `GET https://example.com/cds-services`
 
@@ -589,4 +589,4 @@ As another example, an extension defined on the discovery response could look li
   ]
 }
 ```
-[OAuth 2.0]: https://oauth.net/2/
+[OAuth 2.0]: https://oauth.net/2/