Removed s from file names in examples to match file directories.

Author: David Brown

README.md

@@ -50,7 +50,7 @@ cd amazon-cloudfront-functions/
 aws cloudfront create-function \
 --name add-cache-control-headers \
 --function-config Comment="Function to add cache-control headers",Runtime=cloudfront-js-1.0 \
---function-code fileb://add-cache-control-headers/index.js
+--function-code fileb://add-cache-control-header/index.js
 
 {
     "Location": "https://cloudfront.amazonaws.com/2020-05-31/function/arn:aws:cloudfront::XXXXXXXXXXXX:function/add-cache-control-headers",
@@ -83,7 +83,7 @@ Test the function using the provided test event by running the following command
 aws cloudfront test-function \
 --name add-cache-control-headers \ 
 --if-match EXXXXXXXXX \
---event-object fileb://add-cache-control-headers/test-event.json
+--event-object fileb://add-cache-control-header/test-event.json
 
 {
     "TestResult": {

add-cache-control-header/README.md

@@ -13,7 +13,7 @@ If your origin sends a `Cache-Control` header in responses to CloudFront, this h
 To validate that the function is working as expected, you can use the provided `test-event.json` test object. To test, you can use the `test-function` CLI command that will look something like this:
 
 ```
-$ aws cloudfront test-function --if-match EXXXXXXXXXXXX --name add-cache-control-headers --event-object fileb://add-cache-control-headers/test-event.json
+$ aws cloudfront test-function --if-match EXXXXXXXXXXXX --name add-cache-control-headers --event-object fileb://add-cache-control-header/test-event.json
 ```
 
 If the function has been set up correctly, you should see a result similar to the following with the `cache-control` header being added in the `FunctionOutput` JSON object: