Skip to content

Commit 8838e58

Browse files
authored
Add space after 'Understanding Scaling Behavior'
1 parent 81a2bd0 commit 8838e58

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

doc_source/concurrent-executions.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ You can optionally set the concurrent execution limit for a function\. You may c
2424
+ If your function connects to VPC based resources, you must make sure your subnets have adequate address capacity to support the ENI scaling requirements of your function\. You can estimate the approximate ENI capacity with the following formula:
2525

2626
Where:
27-
+ **Concurrent execution** – This is the projected concurrency of your workload\. Use the information in [Understanding Scaling Behavior](scaling.md)to determine this value\.
27+
+ **Concurrent execution** – This is the projected concurrency of your workload\. Use the information in [Understanding Scaling Behavior](scaling.md) to determine this value\.
2828
+ **Memory in GB** – The amount of memory you configured for your Lambda function\.
2929

3030
You can set the concurrent execution limit for a function to match the subnet size limits you have\.
@@ -98,4 +98,4 @@ To understand your concurrent execution usage, AWS Lambda provides the following
9898
+ **ConcurrentExecutions:** This shows you the concurrent executions at an account level, and for any function with a custom concurrency limit\.
9999
+ **UnreservedConcurrentExecutions:** This shows you the total concurrent executions for functions assigned to the default “unreserved” concurrency pool\.
100100

101-
To learn about these metrics and how to access them, see [Using Amazon CloudWatch](monitoring-functions.md)\.
101+
To learn about these metrics and how to access them, see [Using Amazon CloudWatch](monitoring-functions.md)\.

0 commit comments

Comments
 (0)