Merge branch 'feature/updated-chain-metadata' of github.com:pinax-net…

…work/chains-metadata into feature/updated-chain-metadata

docs/proposals/ops-product-sync.md

@@ -8,12 +8,12 @@ This document is a proposal for syncing the OPS and Product teams. The goal is t
 
 The OPS team maintains a private list (in a YAML file in the OPS Github organization) of chains supported or to-be-supported by Pinax. This list needs to be maintained as it triggers a series of automations on the ops side.
 
-The OPS team also maintains a Notion page on The Graph's side, which contains the list of chains supported by Pinax products.
-
 The Product team maintains this repository, which acts as the single-source-of-truth for Pinax products. It contains extra metadata that is not present in the OPS list, such as chain icons, __chain services__, and other product-specific information.
 
 Those two lists are already necessary for their respective teams.
 
+The OPS team also maintains a Notion page on The Graph's side, which contains the list of chains supported by Pinax products.
+
 ### Data duplication
 
 To further avoid maintaining the same data in two different places, here's the data that each team currently maintains. It would be beneficial to understand which team is responsible for which piece of data.
@@ -85,4 +85,4 @@ The OPS team will maintain the private list as they do now and a GitHub Action,
 
 The Product team can then leverage the public endpoint and Github Actions on their side too.
 
-Depending on the data the OPs team can provide and if The Graph accepts it, the Product team could work on an automated alternative to the current manual process of updating the Notion page.
+Depending on the data the OPs team can provide and if The Graph accepts it, the Product team could work on an automated alternative to the current manual process of updating the Notion page.