Recategorize Rover docs slightly

docs/gatsby-config.js

@@ -14,22 +14,20 @@ module.exports = {
         sidebarCategories: {
           null: [
             'index',
-          ],
-          'Setup': [
             'getting-started',
             'configuring',
             'ci-cd',
+            'essentials',
             'privacy',
+            'contributing',
           ],
-          'Usage': [
-            'essentials',
+          'Base Commands': [
+            'graphs',
+          ],
+          'Federation Commands': [
             'subgraphs',
             'supergraphs',
-            'graphs',
           ],
-          'Community': [
-            'contributing',
-          ]
         },
       },
     },

docs/source/ci-cd.md

@@ -1,9 +1,9 @@
 ---
-title: "Setting up CI/CD workflows with Rover"
+title: "Using Rover in CI/CD"
 sidebar_title: "CI/CD"
 ---
 
-You can use the Rover CLI in any CI/CD environment that uses any supported operating system (Linux, MacOS, or Windows).
+You can use Rover in any CI/CD environment that uses a Rover-supported operating system (Linux, MacOS, or Windows). Most commonly, this is to run [schema checks](https://www.apollographql.com/docs/studio/schema-checks/) with [`rover graph check`](./graphs/#checking-schema-changes) or [`rover subgraph check`](./subgraphs/#checking-subgraph-schema-changes).
 
 Rover can be installed like many other CLI tools, but the installation method varies depending on which provider you're using. We've included instructions for two of the most common CI/CD providers, [CircleCI](https://circleci.com/) and [GitHub Actions](https://github.com/features/actions).
 

docs/source/graphs.md

@@ -1,10 +1,10 @@
 ---
-title: 'Working with non-federated graphs'
-sidebar_title: 'Non-federated graphs'
-description: '(Graphs represented by a monolithic GraphQL server)'
+title: 'Working with graphs'
+sidebar_title: 'graph'
+description: 'Publish and retrieve your API schema'
 ---
 
-> This article applies only to non-federated graphs. When working with a federated graph, see [Working with subgraphs](./subgraphs).
+> These commands are for graphs that do _not_ use [federation](https://www.apollographql.com/docs/federation/). When working with a federated graph, instead use the [`subgraph` comamand](./subgraphs).
 
 ## Fetching a schema
 

docs/source/index.mdx

@@ -12,7 +12,7 @@ import { colors } from 'gatsby-theme-apollo-core';
 >
 > For details, see [Public preview](#public-preview).
 
-**Rover** is a CLI for managing and maintaining data graphs with [Apollo Studio](https://www.apollographql.com/docs/studio/). It helps you safely publish and fetch GraphQL schemas (both [federated](./subgraphs/) and [non-federated](./graphs/)) from the Apollo schema registry.
+**Rover** is a CLI for managing and maintaining data graphs with [Apollo Studio](https://www.apollographql.com/docs/studio/). It helps you safely publish and fetch GraphQL schemas (both [monolithic](./graphs/) and [federated](./subgraphs/)) from the Apollo schema registry.
 
 Upon full release, Rover will replace the existing [Apollo CLI](https://www.apollographql.com/docs/devtools/cli/) as the primary command-line tool for communicating with Studio.
 

docs/source/subgraphs.md

@@ -1,6 +1,6 @@
 ---
 title: 'Working with subgraphs'
-sidebar_title: 'Subgraphs (federated)'
+sidebar_title: 'subgraph'
 description: 'in a federated architecture'
 ---
 
@@ -189,7 +189,7 @@ If you're running a subgraph that hasn't been deployed yet or isn't using manage
 </tbody>
 </table>
 
-## Checking subgraph changes
+## Checking subgraph schema changes
 
 > Schema checks require a [paid plan](https://www.apollographql.com/pricing).
 

docs/source/supergraphs.md

@@ -1,6 +1,6 @@
 ---
 title: 'Working with supergraphs'
-sidebar_title: 'Supergraphs (federated)'
+sidebar_title: 'supergraph'
 description: 'in a federated architecture'
 ---