From b9fcc0867e45d2c1e75d8006fb08f20770d0285a Mon Sep 17 00:00:00 2001
From: github-actions <41898282+github-actions[bot]@users.noreply.github.com>
Date: Fri, 2 Jun 2023 14:34:39 +0000
Subject: [PATCH] Transpile fa3a30a5

---
 docs/modules/ROOT/pages/crosschain.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/modules/ROOT/pages/crosschain.adoc b/docs/modules/ROOT/pages/crosschain.adoc
index cbe24df77..fd6367c64 100644
--- a/docs/modules/ROOT/pages/crosschain.adoc
+++ b/docs/modules/ROOT/pages/crosschain.adoc
@@ -52,7 +52,7 @@ This token is mintable and upgradeable by the owner of the contract.
 
 Let's now imagine that this contract is going to live on one chain, but we want the minting and the upgrading to be performed by a xref:governance.adoc[`governor`] contract on another chain.
 
-For example, we could have our token on xDai, with our governor on mainnet, or we could have our token on mainnet, with our governor on optimism
+For example, we could have our token on xDai, with our governor on mainnet, or we could have our token on mainnet, with our governor on optimism.
 
 In order to do that, we will start by adding xref:api:crosschain.adoc#CrossChainEnabled[`CrossChainEnabled`] to our contract. You will notice that the contract is now abstract. This is because `CrossChainEnabled` is an abstract contract: it is not tied to any particular chain and it deals with cross-chain interactions in an abstract way. This is what enables us to easily reuse the code for different chains. We will specialize it later by inheriting from a chain-specific implementation of the abstraction.