From 7ae8d09ae03cbe91d99ca113e19ec56641b737f5 Mon Sep 17 00:00:00 2001 From: Nic Volanschi Date: Thu, 1 Aug 2024 09:35:51 +0200 Subject: [PATCH 1/3] doc: discourage use of contract as a synonym of account --- docs/alpha/glossary.rst | 3 --- 1 file changed, 3 deletions(-) diff --git a/docs/alpha/glossary.rst b/docs/alpha/glossary.rst index ae1c13ad5d00..997654e23718 100644 --- a/docs/alpha/glossary.rst +++ b/docs/alpha/glossary.rst @@ -163,9 +163,6 @@ _`Burn` _`Constant` Protocols are parameterized by several parameters called protocol constants, which may vary from one protocol to another or from one network to another. -_`Contract` - See account_. - .. _def_cycle_alpha: _`Cycle` -- GitLab From 5a47f1494bf235c550c015b4d35d14e103cea9cc Mon Sep 17 00:00:00 2001 From: Nic Volanschi Date: Thu, 1 Aug 2024 15:42:34 +0200 Subject: [PATCH 2/3] doc: refer to the client man in howtouse#client --- docs/introduction/howtouse.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/introduction/howtouse.rst b/docs/introduction/howtouse.rst index 4e5679850112..236230b1aa5f 100644 --- a/docs/introduction/howtouse.rst +++ b/docs/introduction/howtouse.rst @@ -284,7 +284,7 @@ protocol run by the node. For instance, ``get timestamp`` isn't available when the node runs the genesis protocol, which may happen for a few minutes when launching a node for the first time. -The behaviour of the client can be customized using various mechanisms, including command-line options, a configuration file, and environment variables. For details, refer to :doc:`../user/setup-client`. +The behaviour of the client can be customized using various mechanisms, including command-line options, a configuration file, and environment variables. For details, refer to the :ref:`client manual ` and :doc:`client set-up instructions <../user/setup-client>`. A Simple Wallet ~~~~~~~~~~~~~~~ -- GitLab From b083e4944e385028fdd2735573cf2a8926a720bb Mon Sep 17 00:00:00 2001 From: Nic Volanschi Date: Fri, 9 Aug 2024 09:45:49 +0200 Subject: [PATCH 3/3] doc: replace Octez/Tezos node --- docs/developer/rpc.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/developer/rpc.rst b/docs/developer/rpc.rst index c2f48f50529e..5dbbd48cc5b9 100644 --- a/docs/developer/rpc.rst +++ b/docs/developer/rpc.rst @@ -23,7 +23,7 @@ To address the problem of heavy RPC requests, the RPC interface can be activated in two different modes. - Local RPC server: this server operates in the same process as the - Tezos node and serves data directly from the node. + Octez node and serves data directly from the node. - External RPC server: this server operates in a separate process and forwards requests to the Local RPC server. However, some RPC requests are handled directly by the External RPC server, which we @@ -51,7 +51,7 @@ Service provider setup: - Heavy load - Slow/heavy individual RPC requests are probable and can significantly impact the service availability -In both cases, the total load generated by the RPC requests on the Tezos node +In both cases, the total load generated by the RPC requests on the Octez node is important. However, in baking setup the heavy individual RPC requests are unlikely and thus enabling External RPC server will have minor or no benefit. For a service provider, enabling the External RPC server is essential to ensure the node @@ -139,7 +139,7 @@ External RPC server ------------------- Thanks to this feature, the node won't experience slowdowns on computationally -intensive RPC calls. This significantly reduces the load on the Tezos node and +intensive RPC calls. This significantly reduces the load on the Octez node and prevents it from stopping synchronization with its peers or becoming out of sync. Additionally, performance is expected to be slightly increased in terms of requests handled per second. The External RPC server increases the latency for the RPC requests -- GitLab