#237: Clarified prefetch authorization conformance language.

Author: brynrhodes

docs/specification/1.0.md

@@ -224,7 +224,7 @@ An EHR MAY choose to honor some or all of the desired prefetch templates, and is
 - The EHR MAY compute an efficient set of prefetch templates from multiple CDS Services, thereby reducing the number of calls to a minimum
 - The EHR MAY satisfy some of the desired prefetched templates via some internal service or even its own FHIR server.
 
-The EHR SHALL deny access if the requested resource is outside the user's authorized scope.
+The EHR SHALL deny access to the request resource if it is outside the user's authorized scope.
 
 As part of preparing the request, an EHR processes each prefetch template it intends to satisfy by replacing the prefetch tokens in the prefetch template to construct a relative FHIR request URL. This specification is not prescriptive about how this request is actually processed. The relative URL may be appended to the base URL for the EHR's FHIR server and directly invoked, or the EHR may use internal infrastructure to satisfy the request in the same way that invoking against the FHIR server would.