update repo links

Signed-off-by: Matt Rice <[email protected]>
across-protocol · Sep 30, 2024 · f7a25fc · f7a25fc
1 parent c95d0e7
commit f7a25fc
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/ERCS/erc-7683.md b/ERCS/erc-7683.md
@@ -76,7 +76,7 @@ struct OnchainCrossChainOrder {
 
 Cross-chain execution systems implementing this standard SHOULD use a sub-type that can be parsed from the arbitrary `orderData` field. This may include information such as the tokens involved in the transfer, the destination chain IDs, fulfillment constraints or settlement oracles.
 
-All sub-types SHOULD be registered in the [Order Subtypes Repo](github.com/erc-7683/order-subtypes) to encourage sharing of sub-types based on their functionality. See the examples section for an example of how sub-types can be used to support behavior like executing calldata on a target contract of the user's choice on the destination chain.
+All sub-types SHOULD be registered in the [Subtypes Repo](github.com/ERC-7683/subtypes/tree/main/order-data-subtypes) to encourage sharing of sub-types based on their functionality. See the examples section for an example of how sub-types can be used to support behavior like executing calldata on a target contract of the user's choice on the destination chain.
 
 ### ResolvedCrossChainOrder struct
 
@@ -213,7 +213,7 @@ interface IDestinationSettler {
 
 Cross-chain execution systems implementing this standard SHOULD use a sub-type that can be parsed from the arbitrary `fillerData` field. This may include information such as the desired timing or form of payment for the filler
 
-All sub-types SHOULD be registered in the [Filler Data Subtypes Repo](github.com/erc-7683/filler-data-subtypes) to encourage sharing of sub-types based on their functionality.
+All sub-types SHOULD be registered in the [Subtypes Repo](github.com/ERC-7683/subtypes/tree/main/filler-data-subtypes) to encourage sharing of sub-types based on their functionality.
 
 ## Rationale