Adjust Cache Service Responses text a bit.

Author: jschulte

source/includes/_requirements.md

@@ -62,7 +62,7 @@ Your code should be minimal and perform only actions necessary to bootstrap your
 
 * **Delay Load Content** - A good way to optimize your integration is to do less work on initial page load, and to only do the remaining work on demand. For example, if your integration inserts a Call To Action button, banner or other "point of entry" and when clicked that opens your tool in an overlay, consider waiting to load the code for that overlay until the user clicks the button. You can leverage the API to insert the button with a very small amount of code. When clicked, a function can be called to load the remaining code for your overlay and then fire the initialization routine. This may not be a viable solution for all integrations, but this pattern should be followed whenever possible.
 
-* **Cache Service Responses** - You should consider leveraging <a href="https://developer.mozilla.org/en-US/docs/Web/API/Window/localStorage" target="_blank">local storage</a> or <a href="https://developer.mozilla.org/en-US/docs/Web/API/Window/sessionStorage" target="_blank">session storage</a> to cache data from calls to services required by your integration. Similar to the line item above, if you have a service that returns data, caching that data in the user's browser will avoid having to request it multiple times. This is helpful when users search for vehicles on a site and may see the same vehicle multiple times in different contexts. Reduced calls to your service will reduce network traffic, stress on your service, and will improve the user experience.
+* **Cache Service Responses** - You should set a proper caching policy on services used by your integration to avoid having to make the same request multiple times to a service. Additionally, you could consider leveraging <a href="https://developer.mozilla.org/en-US/docs/Web/API/Window/localStorage" target="_blank">local storage</a> or <a href="https://developer.mozilla.org/en-US/docs/Web/API/Window/sessionStorage" target="_blank">session storage</a> to cache data from calls to services. Similar to the line item above, if you have a service that returns data, caching that data in the user's browser through a caching policy or local storage will avoid having to request it multiple times. This is helpful when users search for vehicles on a site and may see the same vehicle multiple times in different contexts. Reduced calls to your service will reduce network traffic, stress on your service, and will improve the user experience.
 
 * **Use a CDN** - Your bootstrap script and any other integration code or assets should be located on a highly available content delivery network and must work over an HTTPS connection.