From e1980f35fadd9105d70525c82134050649f0959a Mon Sep 17 00:00:00 2001 From: Giovanni Sanchez <108043524+sisyphusSmiling@users.noreply.github.com> Date: Tue, 3 Sep 2024 15:37:20 -0600 Subject: [PATCH] Update cadence/contracts/bridge/FlowEVMBridgeResolver.cdc Co-authored-by: Joshua Hannan --- cadence/contracts/bridge/FlowEVMBridgeResolver.cdc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cadence/contracts/bridge/FlowEVMBridgeResolver.cdc b/cadence/contracts/bridge/FlowEVMBridgeResolver.cdc index 91386a11..8e99e6e0 100644 --- a/cadence/contracts/bridge/FlowEVMBridgeResolver.cdc +++ b/cadence/contracts/bridge/FlowEVMBridgeResolver.cdc @@ -12,7 +12,7 @@ import "FlowEVMBridgeUtils" /// Upon bridging to Cadence, these tokens must have certain basic metadata views that cannot be retrieved at the time /// of bridging, such as MetadataViews.Display for NFTs and FungibleTokenMetadataViews.FTDisplay for FungibleTokens. /// -/// This contract then serves as a means of setting and potentiall updating base placeholder views for these bridged +/// This contract then serves as a means of setting and potentially updating base placeholder views for these bridged /// assets. Anyone wishing to consume the metadata from the source EVM contract should either resolve directly from the /// EVM contract or leverage the EVMBridgedMetadata view which retains the original token URI and/or contract URI (if /// implemented in the source contract).