From 978e545a8efea26e56f148201b4df5d0003cee4d Mon Sep 17 00:00:00 2001
From: Jitendra Kumar <76531339+jitendragangwar123@users.noreply.github.com>
Date: Thu, 16 Nov 2023 10:06:00 +0530
Subject: [PATCH] fix:typo errors

---
 0004-FGTP-Content-Address-EACs.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/0004-FGTP-Content-Address-EACs.md b/0004-FGTP-Content-Address-EACs.md
index c972f3c..3c55bb2 100644
--- a/0004-FGTP-Content-Address-EACs.md
+++ b/0004-FGTP-Content-Address-EACs.md
@@ -13,7 +13,7 @@ Content address EACs
 Data for EACs is currently tracked in several places, including in the 
 [EAC Summary Archive](https://github.com/redransil/filecoin-renewables-purchases/tree/main/EAC_Purchase_Summary_Archive) and the Zero Labs system.
 
-We'd like to take all of the relevant data, including certifictes, and track it with IPDL.
+We'd like to take all of the relevant data, including certificates, and track it with IPDL.
 
 ## Authors
 redransil
@@ -38,7 +38,7 @@ Example #2: [Order sheet](https://github.com/redransil/filecoin-renewables-purch
 ## What are the outputs
 IPLD data stored on [Estuary](https://estuary.tech/) which tracks pdf certificates and associated metadata.
 
-Metadat should include, at least, all of the information returned by a transaction call to the [ZL API](https://proofs-api.zerolabs.green/api/partners/filecoin/nodes/f01234/transactions)
+Metadata should include, at least, all of the information returned by a transaction call to the [ZL API](https://proofs-api.zerolabs.green/api/partners/filecoin/nodes/f01234/transactions)
 
 ## Proposed Solution
 - The pdf certificate should be stored on Estuary and have its own CID: [example](https://bafkreib5dmwkopgu5fb2a572o6x652shwsf45v74xfdvrnllscgunzqese.ipfs.dweb.link/)