From 25d674b77307742e0ea1ac4618d24501a044e9c3 Mon Sep 17 00:00:00 2001 From: Francisco Silva Date: Tue, 31 Dec 2024 10:49:21 +0000 Subject: [PATCH] fixing typo --- tee-worker/omni-executor/parentchain/api-interface/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tee-worker/omni-executor/parentchain/api-interface/README.md b/tee-worker/omni-executor/parentchain/api-interface/README.md index ea53466921..fd149b4b67 100644 --- a/tee-worker/omni-executor/parentchain/api-interface/README.md +++ b/tee-worker/omni-executor/parentchain/api-interface/README.md @@ -9,7 +9,7 @@ The crate exports the generated interface from a scale encoded metadata file. Th #### When to regenerate the interface? Whenever the types of the relevant pallets (OmniAccount, Teebag) change, the interface should be regenerated. This can be done by following the steps in the Generation Process section. -Please note that the metadata fetched from the local node may not be the same as the metadata of the live chains. Therefore, when running the worker agains the live chains, the metadata should be fetched from the live chain and the interface should be regenerated. +Please note that the metadata fetched from the local node may not be the same as the metadata of the live chains. Therefore, when running the worker against the live chains, the metadata should be fetched from the live chain and the interface should be regenerated. ## Generation Process