From 6df83444ecd0eec32185250b753fa8b3ec1da335 Mon Sep 17 00:00:00 2001 From: Patrick Collins <54278053+PatrickAlphaC@users.noreply.github.com> Date: Sat, 16 Nov 2024 12:49:20 -0500 Subject: [PATCH] fix: docs fixtures outdated --- docs/source/core_concepts/named_contracts.rst | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/source/core_concepts/named_contracts.rst b/docs/source/core_concepts/named_contracts.rst index 8defe2c..433e8e1 100644 --- a/docs/source/core_concepts/named_contracts.rst +++ b/docs/source/core_concepts/named_contracts.rst @@ -1,7 +1,7 @@ Named Contracts ################### -One of the major differentiators between moccasin and other smart contract development tools is more flexible and powerful scripting. One of the such cabailities is built in :doc:`fixtures ` and :doc:`named contracts `. +One of the major differentiators between moccasin and other smart contract development tools is more flexible and powerful scripting. One of the such cabailities :doc:`named contracts `. **Named contracts allow you to define deployment scripts, addresses by chain, fixtures settings for testing, and more.** @@ -124,7 +124,6 @@ And running this on ``mainnet-fork`` will get the resulting output: The key here, was the ``mainifest_contract``, which does a lot of things under the hood, including: - Deploys a contract if one doesn't exist -- Allows us to get fixtures for testing - Returns the named contract at it's address if it's on a chain we recognize - Sets up local testing environments for us to test our contracts