Merge pull request serverless#4044 from serverless/fix-link-to-shared-apig-issue

Fix link to shared API Gateway issue

Author: pmuens

docs/providers/aws/guide/services.md

@@ -37,7 +37,7 @@ comments/
 ```
 This makes sense since related functions usually use common infrastructure resources, and you want to keep those functions and resources together as a single unit of deployment, for better organization and separation of concerns.
 
-**Note:** Currently, every service will create a separate REST API on AWS API Gateway.  Due to a limitation with AWS API Gateway, you can only have a custom domain per one REST API.  If you plan on making a large REST API, please make note of this limitation.  Also, [a fix is in the works][https://github.com/serverless/serverless/issues/3078] and is a top priority.
+**Note:** Currently, every service will create a separate REST API on AWS API Gateway.  Due to a limitation with AWS API Gateway, you can only have a custom domain per one REST API.  If you plan on making a large REST API, please make note of this limitation.  Also, [a fix is in the works](https://github.com/serverless/serverless/issues/3078) and is a top priority.
 
 ## Creation