You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/concepts/configuration/configuration_code.rst
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -341,11 +341,11 @@ Configuration
341
341
~~~~~~~~~~~~~
342
342
343
343
To configure traffic encryption, you need to set the special :ref:`URI parameters <index-uri-several-params>` for a particular connection.
344
-
The parameters can be set for the following ``box.cfg`` options and ``nex.box`` method:
344
+
The parameters can be set for the following ``box.cfg`` options and ``net.box`` method:
345
345
346
346
* :ref:`box.cfg.listen <cfg_basic-listen>` -- on the server side.
347
-
* :ref:`box.cfg.replication <cfg_replication-replication>`--on the client side.
348
-
* :ref:`net_box_object.connect() <net_box-connect>`--on the client side.
347
+
* :ref:`box.cfg.replication <cfg_replication-replication>` -- on the client side.
348
+
* :ref:`net_box_object.connect() <net_box-connect>` -- on the client side.
349
349
350
350
Below is the list of the parameters.
351
351
In the :ref:`next section <configuration_code_iproto-encryption-config-sc>`, you can find details and examples on what should be configured on both the server side and the client side.
0 commit comments