Merge pull request #29 from micheleangioni/patch-1

Fixed typo

Author: mwunderl

doc_source/accessing-resources.md

@@ -4,7 +4,7 @@ Lambda does not enforce any restrictions on your function logic – if you can c
 
 ## Accessing AWS Services<a name="accessing-aws-services"></a>
 
-To access other AWS services, you can use the AWS SDK \([Node\.js](https://aws.amazon.com/sdk-for-node-js/), [Java](https://aws.amazon.com/sdk-for-java/), [Python](https://aws.amazon.com/sdk-for-python/), [C\#\)](https://aws.amazon.com/sdk-for-net/) or [Go](https://aws.amazon.com/sdk-for-go/), AWS Lambda will automatically set the credentials required by the SDK to those of the IAM role associated with your function – you do not need to take any additional steps\. For example, here’s sample code using the Python SDK for accessing an S3 object\.:
+To access other AWS services, you can use the AWS SDK \([Node\.js](https://aws.amazon.com/sdk-for-node-js/), [Java](https://aws.amazon.com/sdk-for-java/), [Python](https://aws.amazon.com/sdk-for-python/), [C\#](https://aws.amazon.com/sdk-for-net/) or [Go](https://aws.amazon.com/sdk-for-go/)), AWS Lambda will automatically set the credentials required by the SDK to those of the IAM role associated with your function – you do not need to take any additional steps\. For example, here’s sample code using the Python SDK for accessing an S3 object\.:
 
 ```
 import boto3
@@ -40,4 +40,4 @@ AWS Lambda runs your function code securely within a VPC by default\. However, t
 **Important**  
 AWS Lambda does not support connecting to resources within Dedicated Tenancy VPCs\. For more information, see [Dedicated VPCs](https://docs.aws.amazon.com/vpc/latest/userguide/dedicated-instance.html)\. 
 
-To learn how to configure a Lambda function to access resources within a VPC, see [Configuring a Lambda Function to Access Resources in an Amazon VPC](vpc.md)
+To learn how to configure a Lambda function to access resources within a VPC, see [Configuring a Lambda Function to Access Resources in an Amazon VPC](vpc.md)