diff --git a/README.md b/README.md
index 88bcf91..5a31226 100644
--- a/README.md
+++ b/README.md
@@ -174,7 +174,7 @@ If you are rebuilding the function or deploying it manually instead of using the
     ```
     >Please note the labelled version in Github does not include any user queries.
 1. Create a Lambda function, and upload the zip file generated by the build script. some of the parameters of the function are:
-    * Runtime: Python 3.6
+    * Runtime: Python 3.9
     * Handler: `lambda_function.lambda_handler`
     * Role: Use the role created above
     * Memory: 256MB
@@ -188,9 +188,9 @@ If you are rebuilding the function or deploying it manually instead of using the
 After a period of time, you can check your CloudWatch metrics and create alarms. You can also view the AuroraPostgresAdvancedMonitoringDashboard that was created as part of the CloudFormation script to visualize the custom metrics.
 
 ![Dashboard1](dashboard1.png)
-![Dashboard2](dashboard2.png)
+![Dashboard2](dashboard2.PNG)
 
-If the metrics are not being emitted properly after deploying the solution, send a test event to the Lambda function with a JSON payload similar to [the one shown above](#EventJson) where Debug is set to True (update parameters to match your environment). This will log additional details to help you uncover the cause of the failure. The most common issues are 1) Lack of network connectivity between the Lambda function amd the KMS and Cloudwatch APIs, and 2) Insufficient permissions on the database. [Review the Pre-Requisites](#PreReqs) for solutions to these issues.
+If the metrics are not being emitted properly after deploying the solution, send a test event to the Lambda function with a JSON payload similar to [the one shown above](#EventJson) where Debug is set to True (update parameters to match your environment). This will log additional details to help you uncover the cause of the failure. The most common issues are 1) Lack of network connectivity between the Lambda function and the KMS and Cloudwatch APIs, and 2) Insufficient permissions on the database. [Review the Pre-Requisites](#PreReqs) for solutions to these issues.
 
 ## <a name="MetricDefinitions"></a>Metric Definitions
 
diff --git a/deploy-non-vpc.yaml b/deploy-non-vpc.yaml
index c84961f..719994f 100644
--- a/deploy-non-vpc.yaml
+++ b/deploy-non-vpc.yaml
@@ -55,7 +55,7 @@ Resources:
     Type: AWS::Serverless::Function
     Properties:
       Handler: lambda_function.lambda_handler
-      Runtime: python3.6
+      Runtime: python3.9
       CodeUri:
         Bucket: !Sub paramsey-cfn-${AWS::Region}
         Key: AuroraPostgresAdvancedMonitoring/aurora-postgres-advanced-monitoring-1.0.zip
diff --git a/deploy-vpc.yaml b/deploy-vpc.yaml
index 4476258..2bfe618 100644
--- a/deploy-vpc.yaml
+++ b/deploy-vpc.yaml
@@ -63,7 +63,7 @@ Resources:
     Type: AWS::Serverless::Function
     Properties:
       Handler: lambda_function.lambda_handler
-      Runtime: python3.6
+      Runtime: python3.9
       CodeUri:
         Bucket: !Sub paramsey-cfn-${AWS::Region}
         Key: AuroraPostgresAdvancedMonitoring/aurora-postgres-advanced-monitoring-1.0.zip