DOCSP-51393 Add connection limit solutions (#13420)

* DOCSP-50487 Add tip on HTTPS URLs and Warning about HTTP + Postman

* DOCSP-50487 typo fixes

* DOCSP-51393 update connection limits section

* DOCSP-51393 fix small error

* DOCSP-51393 correct links

* DOCSP-51393 new links approach

* DOCSP-51393 trying refs again

---------

Co-authored-by: Kevin Meyer <[email protected]>

Author: t-anchor

content/atlas/source/reference/atlas-limits.txt

@@ -95,13 +95,16 @@ total number of connections |service| can allocate for a given query.
 Increase Connection Limit
 ~~~~~~~~~~~~~~~~~~~~~~~~~
 
-If you need to increase the number of connections your |service| cluster can handle,
-consider upgrading your :ref:`cluster tier <scale-cluster-instance>`.
+.. note::
+
+  Atlas scales on memory and compute use, not on connections. However, increased active connections may increase load, which may create need to scale your cluster if other solutions are not viable.
+
+If you are nearing or have reached the maximum number of connections your |service| cluster can handle, you have several options available to redistribute connections or increase your limit:
 
-If your application dynamically creates additional connections, as it might if,
-for example, your database worker pool is elastic, consider enabling 
-:ref:`Cluster Autoscaling <cluster-autoscaling>` to ensure that your |service| 
-cluster can accomodate your dynamic connection count requirement. 
+- :ref:`Tune your application <performance-tuning>` to optimize connection usage.
+- :ref:`Enable connection pooling <connection-pool-overview>` in your application.
+- :ref:`Enable cluster auto-scaling <cluster-autoscaling>` to automatically scale your application as needed. This option is particularly helpful if your application dynamically creates additional connections. An elastic database worker pool would be an example of such an application. 
+- Permanently upgrade your :ref:`cluster tier <scale-cluster-instance>`. 
 
 .. tabs::