Fix few typos & add SNI in connection docs

docs/reference/connection.rst

@@ -205,14 +205,14 @@ for production), or rely on ``edgedb project`` (recommended for development).
    such, explicitly provided parameters are given the highest priority.
 
    In the context of the client libraries, this means passing an option
-   explicitly into the ``connect`` call. Here's how this looks using the
+   explicitly into the ``client creation`` call. Here's how this looks using the
    JavaScript library:
 
    .. code-block:: javascript
 
       import * as edgedb from "edgedb";
 
-      const pool = await edgedb.connect({
+      const pool = await edgedb.createClient({
         instance: "my_instance"
       });
 
@@ -318,6 +318,8 @@ instance-level configuration object.
       - ``--password <pass>``
     * - ``EDGEDB_TLS_CA_FILE``
       - ``--tls-ca-file <path>``
+    * - ``EDGEDB_TLS_SERVER_NAME``
+      - ``--tls-server-name``
     * - ``EDGEDB_CLIENT_TLS_SECURITY``
       - ``--tls-security``
     * - ``EDGEDB_CLIENT_SECURITY``
@@ -373,14 +375,19 @@ instance-level configuration object.
   and provide a path to its location on the filesystem. Otherwise TLS will fail
   to connect.
 
+**EDGEDB_TLS_SERVER_NAME**
+  Sometimes the target instance address cannot be resolved correctly
+  from a hostname. In those cases it is required to provide SNI for proper TLS
+  verification. It is also required for tenant selection in a multi-tenant environment.
+
 **EDGEDB_CLIENT_TLS_SECURITY**
   Sets the TLS security mode. Determines whether certificate and hostname
   verification is enabled. Possible values:
 
   - ``"strict"`` (**default**) — certificates and hostnames will be verified
   - ``"no_host_verification"`` — verify certificates but not hostnames
   - ``"insecure"`` — client libraries will trust self-signed TLS certificates.
-    useful for self-signed or custom certificates.
+    Useful for self-signed or custom certificates.
 
   This setting defaults to ``"strict"`` unless a custom certificate is
   supplied, in which case it is set to ``"no_host_verification"``.
@@ -419,7 +426,7 @@ modified DSN: ``edgedb://newuser:[email protected]:5656``.
 Overriding across priority levels
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-This override behavior only happens *same or lower priority level*. For
+Override behavior can only happen at the *same or lower priority level*. For
 instance:
 
 - ``EDGEDB_PASSWORD`` **will** override the password specified in