Fixing link

Author: Oxyjun

src/content/docs/d1/best-practices/import-export-data.mdx

@@ -7,7 +7,7 @@ sidebar:
 
 D1 allows you to import existing SQLite tables and their data directly, enabling you to migrate existing data into D1 quickly and easily. This can be useful when migrating applications to use Workers and D1, or when you want to prototype a schema locally before importing it to your D1 database(s).
 
-D1 also allows you to export a database. This can be useful for [local development](/d1/features/local-development/) or testing.
+D1 also allows you to export a database. This can be useful for [local development](d1/best-practices/local-development/) or testing.
 
 ## Import an existing database
 

src/content/docs/d1/best-practices/read-replication.mdx

@@ -16,7 +16,7 @@ By using Sessions API for read replication, all of your queries from a single Se
 
 To use read replication with the following Worker code and Sessions API:
 
-1. [Enable read replication](/d1/features/read-replication/#enable-read-replication)
+1. [Enable read replication](d1/best-practices/read-replication/#enable-read-replication)
 2. Select `Deploy to Workers`.
 
 {/* Deploy to Workers button */}
@@ -160,13 +160,13 @@ async function resetTables(session: D1DatabaseSession) {
 
 When using D1 without read replication, D1 routes all queries (both read and write) to a specific database instance in [one location in the world](/d1/configuration/data-location/), known as the primary database instance. D1 request latency is dependent on the physical closeness of a user to the primary database instance. Users located further away from the primary database instance experience longer request latency due to [network round-trip time](https://www.cloudflare.com/learning/cdn/glossary/round-trip-time-rtt/).
 
-When using read replication, D1 introduces multiple “almost up-to-date” copies of the primary database instance which only serve read requests, called <GlossaryTooltip term="read replica"> read replicas </GlossaryTooltip>. D1 creates the read replicas in multiple regions throughout the world [across the Cloudflare network](/d1/features/read-replication/#read-replica-locations).
+When using read replication, D1 introduces multiple “almost up-to-date” copies of the primary database instance which only serve read requests, called <GlossaryTooltip term="read replica"> read replicas </GlossaryTooltip>. D1 creates the read replicas in multiple regions throughout the world [across the Cloudflare network](d1/best-practices/read-replication/#read-replica-locations).
 
 A user may be located far away from the primary database instance but close to a read replica. When D1 routes read requests to the read replica instead of the primary database instance, the user enjoys shorter read request response times.
 
 D1 asynchronously replicates changes from the primary database instance to all read replicas. This means that at any given time, a read replica may be arbitrarily out of date. The time it takes for the latest committed data in the primary database instance to be replicated to the read replica is known as the <GlossaryTooltip term="replica lag"> replica lag </GlossaryTooltip>.
 
-It is replica lag and non-deterministic routing to individual replicas that can lead to application data consistency issues, which Sessions API help handle by ensuring sequential consistency. For more information refer to [Replica lag and consistency model](/d1/features/read-replication/#replica-lag-and-consistency-model).
+It is replica lag and non-deterministic routing to individual replicas that can lead to application data consistency issues, which Sessions API help handle by ensuring sequential consistency. For more information refer to [Replica lag and consistency model](d1/best-practices/read-replication/#replica-lag-and-consistency-model).
 
 :::note
 All write queries are still forwarded to the primary database instance. Read replication only improves the query response time for read requests.
@@ -379,7 +379,7 @@ const result = await session.run()
 
 {/* #### Example of using `bookmark`
 
-This example follows from [Example of using `first-primary`](/d1/features/read-replication/#example-of-using-first-primary), but retrieves the `bookmark` from HTTP cookie.
+This example follows from [Example of using `first-primary`](d1/best-practices/read-replication/#example-of-using-first-primary), but retrieves the `bookmark` from HTTP cookie.
 
 ```ts collapse={1-10, 22-42, 61-86}
 import { ListBillStatementsResult, GetBillStatementResult, Bill } from './types';

src/content/docs/d1/configuration/data-location.mdx

@@ -75,4 +75,4 @@ With read replication enabled, D1 creates and distributes read-only copies of th
 
 When using D1 read replication, D1 automatically creates a read replica in [every available region](/d1/configuration/data-location#available-location-hints), including the region where the primary database instance is located.
 
-Refer to [D1 read replication](/d1/features/read-replication/) for more information.
+Refer to [D1 read replication](d1/best-practices/read-replication/) for more information.

src/content/docs/d1/examples/query-d1-from-python-workers.mdx

@@ -126,4 +126,4 @@ If you receive an error deploying:
 
 - Refer to [Workers Python documentation](/workers/languages/python/) to learn more about how to use Python in Workers.
 - Review the [D1 Workers Binding API](/d1/worker-api/) and how to query D1 databases.
-- Learn [how to import data](/d1/features/import-export-data/) to your D1 database.
+- Learn [how to import data](d1/best-practices/import-export-data/) to your D1 database.

src/content/docs/d1/index.mdx

@@ -26,7 +26,7 @@ D1 is Cloudflare's managed, serverless database with SQLite's SQL semantics, bui
 
 D1 is designed for horizontal scale out across multiple, smaller (10 GB) databases, such as per-user, per-tenant or per-entity databases. D1 allows you to build applications with thousands of databases at no extra cost for isolating with multiple databases. D1 pricing is based only on query and storage costs.
 
-Create your first D1 database by [following the Get started guide](/d1/get-started/), learn how to [import data into a database](/d1/features/import-export-data/), and how to [interact with your database](/d1/worker-api/) directly from [Workers](/workers/) or [Pages](/pages/functions/bindings/#d1-databases).
+Create your first D1 database by [following the Get started guide](/d1/get-started/), learn how to [import data into a database](d1/best-practices/import-export-data/), and how to [interact with your database](/d1/worker-api/) directly from [Workers](/workers/) or [Pages](/pages/functions/bindings/#d1-databases).
 
 ***
 

src/content/docs/d1/observability/metrics-analytics.mdx

@@ -32,7 +32,7 @@ Metrics can be queried (and are retained) for the past 31 days.
 D1 returns the number of rows read, rows written (or both) in response to each individual query via [the Workers Binding API](/d1/worker-api/return-object/).
 
 Row counts are a precise count of how many rows were read (scanned) or written by that query.
-Inspect row counts to understand the performance and cost of a given query, including whether you can reduce the rows read [using indexes](/d1/features/use-indexes/). Use query counts to understand the total volume of traffic against your databases and to discern which databases are actively in-use.
+Inspect row counts to understand the performance and cost of a given query, including whether you can reduce the rows read [using indexes](d1/best-practices/use-indexes/). Use query counts to understand the total volume of traffic against your databases and to discern which databases are actively in-use.
 
 Refer to the [Pricing documentation](/d1/platform/pricing/) for more details on how rows are counted.
 
@@ -322,5 +322,5 @@ npx wrangler d1 insights <database_name> --sort-type=sum --sort-by=writes --limi
 :::note
 The quantity `queryEfficiency` measures how efficient your query was. It is calculated as: the number of rows returned divided by the number of rows read.
 
-Generally, you should try to get `queryEfficiency` as close to `1` as possible. Refer to [Use indexes](/d1/features/use-indexes/) for more information on efficient querying.
+Generally, you should try to get `queryEfficiency` as close to `1` as possible. Refer to [Use indexes](d1/best-practices/use-indexes/) for more information on efficient querying.
 :::

src/content/docs/d1/platform/pricing.mdx

@@ -64,7 +64,7 @@ Yes, any queries you run against your database, including inserting (`INSERT`) e
 
 ### Can I use an index to reduce the number of rows read by a query?
 
-Yes, you can use an index to reduce the number of rows read by a query. [Creating indexes](/d1/features/use-indexes/) for your most queried tables and filtered columns reduces how much data is scanned and improves query performance at the same time. If you have a read-heavy workload (most common), this can be particularly advantageous. Writing to columns referenced in an index will add at least one (1) additional row written to account for updating the index, but this is typically offset by the reduction in rows read due to the benefits of an index.
+Yes, you can use an index to reduce the number of rows read by a query. [Creating indexes](d1/best-practices/use-indexes/) for your most queried tables and filtered columns reduces how much data is scanned and improves query performance at the same time. If you have a read-heavy workload (most common), this can be particularly advantageous. Writing to columns referenced in an index will add at least one (1) additional row written to account for updating the index, but this is typically offset by the reduction in rows read due to the benefits of an index.
 
 ### Does a freshly created database, and/or an empty table with no rows, contribute to my storage?
 

src/content/docs/d1/reference/backups.mdx

@@ -86,7 +86,7 @@ wrangler d1 backup download example-db 123a81a2-ab91-4c2e-8ebc-64d69633faf1
 🌀 Done!
 ```
 
-The database backup will be download to the current working directory in native SQLite3 format. To import a local database, read [the documentation on importing data](/d1/features/import-export-data/) to D1.
+The database backup will be download to the current working directory in native SQLite3 format. To import a local database, read [the documentation on importing data](d1/best-practices/import-export-data/) to D1.
 
 ## Restoring a backup
 

src/content/docs/d1/reference/generated-columns.mdx

@@ -10,7 +10,7 @@ D1 allows you to define generated columns based on the values of one or more oth
 
 This allows you to normalize your data as you write to it or read it from a table, making it easier to query and reducing the need for complex application logic.
 
-Generated columns can also have [indexes defined](/d1/features/use-indexes/) against them, which can dramatically increase query performance over frequently queried fields.
+Generated columns can also have [indexes defined](d1/best-practices/use-indexes/) against them, which can dramatically increase query performance over frequently queried fields.
 
 ## Types of generated columns
 

src/content/docs/d1/sql-api/foreign-keys.mdx

@@ -16,7 +16,7 @@ By default, D1 enforces that foreign key constraints are valid within all querie
 
 ## Defer foreign key constraints
 
-When running a [query](/d1/worker-api/), [migration](/d1/reference/migrations/) or [importing data](/d1/features/import-export-data/) against a D1 database, there may be situations in which you need to disable foreign key validation during table creation or changes to your schema.
+When running a [query](/d1/worker-api/), [migration](/d1/reference/migrations/) or [importing data](d1/best-practices/import-export-data/) against a D1 database, there may be situations in which you need to disable foreign key validation during table creation or changes to your schema.
 
 D1's foreign key enforcement is equivalent to SQLite's `PRAGMA foreign_keys = on` directive. Because D1 runs every query inside an implicit transaction, user queries cannot change this during a query or migration.