From 5134dafb8e5184aeed73be30066f8e22591e0254 Mon Sep 17 00:00:00 2001 From: Callis Ezenwaka Date: Thu, 17 Feb 2022 00:28:34 +0100 Subject: [PATCH] Update typo in using-for.rst Update typo in using-for.rst --- docs/assembly.rst | 2 +- docs/contracts/using-for.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/assembly.rst b/docs/assembly.rst index 5427e0f51..e6dc6519c 100644 --- a/docs/assembly.rst +++ b/docs/assembly.rst @@ -139,7 +139,7 @@ the variable will not point beyond ``calldatasize()`` is performed. For external function pointers the address and the function selector can be accessed using ``x.address`` and ``x.selector``. The selector consists of four right-aligned bytes. -Both values are can be assigned to. For example: +Both values can be assigned to. For example: .. code-block:: solidity :force: diff --git a/docs/contracts/using-for.rst b/docs/contracts/using-for.rst index 582409904..af6750f87 100644 --- a/docs/contracts/using-for.rst +++ b/docs/contracts/using-for.rst @@ -120,7 +120,7 @@ It is also possible to extend elementary types in that way: } Note that all external library calls are actual EVM function calls. This means that -if you pass memory or value types, a copy will be performed, even of the +if you pass memory or value types, a copy will be performed, even in case of the ``self`` variable. The only situation where no copy will be performed is when storage reference variables are used or when internal library functions are called.