diff --git a/docs/012/plugins.rst b/docs/012/plugins.rst index df09bb005b02ce38d05d1aaa87eebf7127e6d131..9f98e55fac7832f33a77703f5301773c08f1b0df 100644 --- a/docs/012/plugins.rst +++ b/docs/012/plugins.rst @@ -182,7 +182,7 @@ The default value of the parameter ``N`` is chosen such that a node will always manager operations to allow the next baker to produce a filled block (if there are enough operations in the network). Its value is currently fixed to 5000. Indeed, the total size occupied by manager operations in a -block is currently bounded by 512 KibiBytes, and ``unset deposits limit`` seems +block is currently bounded by 512 `KiB `_, and ``unset deposits limit`` seems to be the smallest manager operation, with 126 Bytes, so there are at most 512 * 1024 / 126 = 4161 manager operations per block. diff --git a/docs/alpha/plugins.rst b/docs/alpha/plugins.rst index 6d74ff133b1ec4e85b04c52ff70af8d146d71b73..701e09debd8de68f9be33e232b936b828d48e1d0 100644 --- a/docs/alpha/plugins.rst +++ b/docs/alpha/plugins.rst @@ -183,7 +183,7 @@ The default value of the parameter ``N`` is chosen such that a node will always manager operations to allow the next baker to produce a filled block (if there are enough operations in the network). Its value is currently fixed to 5000. Indeed, the total size occupied by manager operations in a -block is currently bounded by 512 KibiBytes, and ``unset deposits limit`` seems +block is currently bounded by 512 `KiB `_, and ``unset deposits limit`` seems to be the smallest manager operation, with 126 Bytes, so there are at most 512 * 1024 / 126 = 4161 manager operations per block. diff --git a/docs/developer/contributing.rst b/docs/developer/contributing.rst index a2ed4843e30f1d0d73177c420bfe37ddf9f74186..f8e5123db4187d76b143662db98b17d6c941abb4 100644 --- a/docs/developer/contributing.rst +++ b/docs/developer/contributing.rst @@ -414,7 +414,7 @@ To find reviewers, either: - Look at authors of the code you are modifying using `git blame `_. - Ask help to the :ref:`merge coordinator `, either - by asking him/here on Slack or mentioning them in a comment (see next paragraph). + by asking him/her on Slack or mentioning them in a comment (see next paragraph). Depending on your `GitLab role `_ you may or may not be able to use the *Reviewers* field for specifying diff --git a/docs/developer/merge_team.rst b/docs/developer/merge_team.rst index 790e04d7acbb15c0a16c8ec0dc2d5bf6168e560a..b4d0f556ef3a65453bee66479737ff6d9a7eda14 100644 --- a/docs/developer/merge_team.rst +++ b/docs/developer/merge_team.rst @@ -2,7 +2,7 @@ Octez Merge Team ================ The Octez merge team is a `group of developers -`_ +`_ from different teams of the Tezos ecosystem. They are automatically selected as approvers when you create a merge diff --git a/docs/developer/proposal_testing.rst b/docs/developer/proposal_testing.rst index b05aa68831c756bcdbbc6111dafc7e0039e6fe4d..d034444a46566f6363b807128cec685d4cc998fa 100644 --- a/docs/developer/proposal_testing.rst +++ b/docs/developer/proposal_testing.rst @@ -348,6 +348,11 @@ we would revert it:: Reversed (or previously applied) patch detected! Assume -R? [n] n Apply anyway? [n] n +.. warning:: + After finishing your migration tests, mind reverting the yes-node patch to obtain a "normal" node; otherwise you may obtain spurious errors. + To do this, you may apply the same patch backwards using + ``patch -p1 --reverse < scripts/yes-node.patch``. + Alternatively, if you are sure that no other changes were done, you can reset the source file using ``git checkout src/lib_crypto/signature.ml``. 5. Compile the Project ~~~~~~~~~~~~~~~~~~~~~~ diff --git a/docs/introduction/howtoget.rst b/docs/introduction/howtoget.rst index bf19483702301f7c84589bf70465939887ffa4db..d985325bf4b184523a697a57c5b3a62643891fcd 100644 --- a/docs/introduction/howtoget.rst +++ b/docs/introduction/howtoget.rst @@ -422,7 +422,9 @@ another location (such as ``/usr/local/bin``), the Tezos binaries may prompt you to install the Zcash parameter files. The easiest way is to download and run this script:: - https://raw.githubusercontent.com/zcash/zcash/master/zcutil/fetch-params.sh + wget https://raw.githubusercontent.com/zcash/zcash/master/zcutil/fetch-params.sh + chmod +x fetch-params.sh + ./fetch-params.sh The node will try to find Zcash parameters in the following directories, in this order: diff --git a/manifest/manifest.mli b/manifest/manifest.mli index 0281be43e1662d3dfcd4ef28a5ce56770ec2561d..bf87dffef1e4ec46717300ac893001e45f248d60 100644 --- a/manifest/manifest.mli +++ b/manifest/manifest.mli @@ -124,7 +124,7 @@ module Dune : sig - [alias_deps] is a list of target aliases to build before this rule. They are added to the [deps] stanza in [alias] stanzas - (resulting in [(deps (alias ...) ...)]. + (resulting in [(deps (alias ...) ...)]). - [deps_dune] can be used to specify the arguments of the [deps] stanza directly as an s-expression instead. @@ -614,7 +614,7 @@ val public_exe : ?internal_name:string -> string maker public names. If not given, the list of internal names is derived from the list of names as for [public_lib]. - @raise [Invalid_arg] if the list of names is empty or if the length of + @raise Invalid_arg if the list of names is empty or if the length of [internal_names] differs from the length of the list of public names. *) val public_exes : ?internal_names:string list -> string list maker @@ -710,7 +710,7 @@ val external_lib : [node_wrapper_flags]: flags to add to the [node_wrapper] executable command in [runtest_js] aliases. Only used for test and executable test targets. - @raise [Invalid_arg] if [main_lib] was not built with [external_lib]. *) + @raise Invalid_arg if [main_lib] was not built with [external_lib]. *) val external_sublib : ?main_module:string -> ?js_compatible:bool ->