Documentation does not include proper plugin name,; needs version warning removed in Sanity Plugin page

[sarahmattar]

Hi @joshredwards , I just installed this in a work project and while it works well, there's still a lot of generic boilerplate in the documentation for usage that hasn't been updated for the plugin's usage. I had to dig into the package to find the name of the plugin, as the docs on Sanity and npm still refer to it as myPlugin({}) instead of ContentModelGraph(). On the Sanity plugin page listing, there is still a warning that the plugin is only compatible with Sanity Studio v2, when it has been updated to v3. I'm not sure if that can be changed on your end or if someone from Sanity has to take it off the "not compatible with v3" list. Updating these details will probably boost plugin adoption significantly!

The good news is once I got it working, it made sense of a moderately complex schema for our CMS use case, which uses a pageBuilder style of fragmenting our schemas to be 1:1 with our components. 😃 It shows the entire schema from a high level, but ideally we want to use it for illustrating prospective schema changes in a PR - is this possible?