Move things around per Olivia's comment

site/docs/concepts/README.md

@@ -247,7 +247,7 @@ A given capture or materialization may have multiple bindings, which connect mul
 Flow [collections](#collections) use cloud storage buckets for the durable storage of data.
 Storage mappings define how Flow maps your various collections into your storage buckets and prefixes.
 
-[Learn more about storage mappings](./storage-mappings/index.md)
+[Learn more about storage mappings](./storage-mappings.md)
 
 
 ## Advanced concepts

site/docs/concepts/advanced/journals.md

@@ -105,7 +105,7 @@ collections:
         retention: 720h
 ```
 
-Your [storage mappings](../storage-mappings/index.md) determine
+Your [storage mappings](../storage-mappings.md) determine
 which of your cloud storage buckets is used
 for storage of collection fragment files.
 

site/docs/concepts/advanced/shards.md

@@ -65,4 +65,4 @@ However, they can hold your user data.
 Recovery logs of [derivations](../derivations.md) hold your derivation register values.
 
 Recovery logs are stored in your cloud storage bucket,
-and must have a configured [storage mapping](../storage-mappings/index.md#recovery-logs).
+and must have a configured [storage mapping](../storage-mappings.md#recovery-logs).

site/docs/concepts/collections.md

@@ -349,7 +349,7 @@ regular JSON files in your cloud storage bucket.
 Reads of that history are served by
 directly reading files from your bucket.
 
-Your [storage mappings](./storage-mappings/index.md)
+Your [storage mappings](./storage-mappings.md)
 determine how Flow collections are mapped into
 your cloud storage buckets.
 

site/docs/concepts/schemas.md

@@ -327,7 +327,7 @@ reduce: { strategy: merge }
 ```
 
 Learn more in the
-[reductions strategies](../../reference/reduction-strategies/)
+[reduction strategies](../../reference/reduction-strategies/)
 reference documentation.
 
 #### Reductions and collection keys

site/docs/concepts/storage-mappings/index.md → site/docs/concepts/storage-mappings.md

@@ -1,13 +1,13 @@
 ---
-sidebar_position: 1
+sidebar_position: 8
 ---
 # Storage mappings
 
 Flow stores the documents that comprise your collections in a cloud storage bucket.
 Your **storage mapping** tells Flow which bucket to use.
 
-Every Flow organization (defined by its [catalog prefix](../catalogs.md#namespace)) has a storage mapping defined during setup.
-When you're provisioned a prefix, your Estuary account manager will help you [set up your storage mapping](../../getting-started/installation.md#configuring-your-cloud-storage-bucket-for-use-with-flow).
+Every Flow organization (defined by its [catalog prefix](./catalogs.md#namespace)) has a storage mapping defined during setup.
+When you're provisioned a prefix, your Estuary account manager will help you [set up your storage mapping](../getting-started/installation.mdx#configuring-your-cloud-storage-bucket-for-use-with-flow).
 If you have a trial account, your storage mapping is Estuary's secure Google Cloud Storage bucket.
 
 You can set up a bucket lifecycle policy to manage data retention in your storage mapping;

site/docs/concepts/web-app.md

@@ -287,7 +287,7 @@ You typically have just one prefix: your organization name, which you provided w
 If you're a trial user, your prefix is `trial/`, and this tab isn't applicable to you;
 your data is stored temporarily in Estuary's cloud storage bucket for your trial period.
 
-[Learn more about storage mappings.](./storage-mappings/index.md)
+[Learn more about storage mappings.](./storage-mappings.md)
 
 #### Connectors