fix(devx): fix typo (#4176)

* fix(devx): fix typo * Update docs/content/developer/evm-to-move/creating-token.mdx Co-authored-by: DaughterOfMars <[email protected]> --------- Co-authored-by: DaughterOfMars <[email protected]>
iotaledger · Nov 21, 2024 · aaf7f0d · aaf7f0d
1 parent 9fa229d
commit aaf7f0d
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/docs/content/developer/evm-to-move/creating-token.mdx b/docs/content/developer/evm-to-move/creating-token.mdx
@@ -42,7 +42,7 @@ The initial creation of `Coin` takes place by minting these coins. This is usual
 
 There's a lot to unpack here; let's look at it piece by piece. In IOTA Move, there is no 'compiler version' defined within the module itself, like in Solidity.
 
-A `module` is defined (`exampletoken`) as part of the `examples` package (modules always reside in packages; a package can have one or more modules in one file or spread out over several files). Within the `module,` we first alias the functionality we wish to use from other modules with `use.` If you don't do this, you would have to explicitly call other modules through their full package path, which would be very verbose and cumbersome. We import an `option` module from the `std` package and some modules from the `iota` package. The `std` and `iota` names are actually mappings as well to other modules defined in the `Move.toml` file of the package as described in the [documentation](../getting-started/create-a-package.mdx).
+A `module` (`exampletoken`) is defined as part of the `examples` package (modules always reside in packages; a package can have one or more modules in one file or spread out over several files). Within the `module,` we first alias the functionality we wish to use from other modules with `use.` If you don't do this, you would have to explicitly call other modules through their full package path, which would be very verbose and cumbersome. We import an `option` module from the `std` package and some modules from the `iota` package, the 'std::option' module is implicitly imported in every module, and you don't need to add an import. The `std` and `iota` names are actually mappings as well to other modules defined in the `Move.toml` file of the package as described in the [documentation](../getting-started/create-a-package.mdx).
 
 After the aliases, we see an empty struct defined:
 

diff --git a/docs/content/developer/evm-to-move/evm-to-move.mdx b/docs/content/developer/evm-to-move/evm-to-move.mdx
@@ -2,6 +2,6 @@
 title: From Solidity/EVM to Move
 ---
 
-Solidity and the Ethereum Virtual Machine (EVM) have been at the core of smart contract development for some years now. Complete ecosystems have been built around it, mainly by bringing the composable building blocks to it to facilitate Decentralised Finance (DeFi). Move is a pretty new contenter in the space, and while certainly not the first attempt to take the place of Solidity it does do a lot of things right that will help developers, projects and end-users to set a new standard when it comes to smart contracts, be it in safety, usability or feature-wise.
+Solidity and the Ethereum Virtual Machine (EVM) have been at the core of smart contract development for some years now. Complete ecosystems have been built around it, mainly by bringing the composable building blocks to it to facilitate Decentralised Finance (DeFi). Move is a pretty new contender in the space, and while certainly not the first attempt to take the place of Solidity it does do a lot of things right that will help developers, projects and end-users to set a new standard when it comes to smart contracts, be it in safety, usability or feature-wise.
 
 If this sounds good to you you are in the right place. This guide will take you through to process of practically applying IOTA Move from a Solidity developer perspective. Let's get started!