renaming diagram as architecture not arcj

Author: nideveloper

README.md

@@ -21,7 +21,7 @@ These patterns are from https://www.jeremydaly.com/serverless-microservice-patte
 ![Architecture](https://raw.githubusercontent.com/cdk-patterns/serverless/master/the-simple-webservice/img/architecture.png)
 
 #### [The Scalable Webhook](/the-scalable-webhook/README.md)
-![Architecture](https://raw.githubusercontent.com/cdk-patterns/serverless/master/the-scalable-webhook/img/arch.png)
+![Architecture](https://raw.githubusercontent.com/cdk-patterns/serverless/master/the-scalable-webhook/img/architecture.png)
 
 ## Pattern Usage
 

the-scalable-webhook/README.md

@@ -8,7 +8,7 @@ sure that your serverless resource doesn't scale up to an amount that it DO
 This is done by putting a queue between them and having a lambda with a throttled concurrency policy pull items off the queue and communicate with your 
 serverless resource at a rate it can handle.
 
-![Architecture](https://raw.githubusercontent.com/cdk-patterns/serverless/master/the-scalable-webhook/img/arch.png)
+![Architecture](https://raw.githubusercontent.com/cdk-patterns/serverless/master/the-scalable-webhook/img/architecture.png)
 
 <strong>NOTE:</strong> For this pattern in the cdk deployable construct I have swapped RDS for DynamoDB. <br /><br />Why? Because it is significantly cheaper/faster for developers to deploy and maintain, I also don't think we lose the essence of the pattern with this swap given we still do the pub/sub deduplication via SQS/Lambda and throttle the subscription lambda. RDS also introduces extra complexity in that it needs to be deployed in a VPC. I am slightly worried developers would get distracted by the extra RDS logic when the main point is the pattern. A real life implementation of this pattern could use RDS MySQL or it could be a call to an on-prem mainframe, the main purpose of the pattern is the throttling to not overload the scale-limited resource.