From f38ae2affd7e9bdab2cc6bc8fe2428abb2013f95 Mon Sep 17 00:00:00 2001 From: madisoncarter1234 Date: Mon, 27 Oct 2025 13:25:42 -0400 Subject: [PATCH] Fix typos in README MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Fix retreiving → retrieving - Fix commited → committed - Fix Composible → Composable --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 40ab0d6..4e01fa0 100644 --- a/README.md +++ b/README.md @@ -36,8 +36,8 @@ See [documentation](https://ourzora.github.io/offchain/) for more examples and t ## Contributing -We welcome contributions that add support for new metadata standards, new ways of retreiving metadata, and ways of normalizing them to a consistent form. -We are commited to integrating contributions to our indexer and making the results available in our API. +We welcome contributions that add support for new metadata standards, new ways of retrieving metadata, and ways of normalizing them to a consistent form. +We are committed to integrating contributions to our indexer and making the results available in our API. You should be able to contribute a new standard for metadata, and have NFTs that adhere to that metadata standard be returned correctly from queries to `api.zora.co`. We hope this helps to foster innovation in how @@ -47,7 +47,7 @@ NFTs are represented, where metadata is stored, and what is expressed in that me - Multiple metadata standards: represent metadata any way you wish - Multiple transport protocols: store metadata where you want -- Composible for custom applications: only parse the standards you care about +- Composable for custom applications: only parse the standards you care about - Future proof: extensible to new formats, locations, etc. The more gigabrain the better. ## Development