Fix broken links (#1443)

docs/develop/app-structure.md

@@ -22,7 +22,7 @@ When creating a cloud environment on AWS/GCP, Encore enables you to configure if
 ## Creating services
 
 To create an Encore service, you create a Go package and
-[define an API](/docs/develop/apis) within it. When using databases, you add database migrations in a subfolder `migrations` to define the structure of the database(s). Learn more in the [SQL databases docs](/docs/develop/databases).
+[define an API](/docs/primitives/apis) within it. When using databases, you add database migrations in a subfolder `migrations` to define the structure of the database(s). Learn more in the [SQL databases docs](/docs/develop/databases).
 
 On disk it might look like this:
 
@@ -40,7 +40,7 @@ On disk it might look like this:
     └── world.go                     // world service code
 ```
 
-<RelatedDocsLink paths={["/docs/primitives/services", "/docs/primitives/apis", "/docs/docs/how-to/share-db-between-services"]} />
+<RelatedDocsLink paths={["/docs/primitives/services", "/docs/primitives/apis", "/docs/how-to/share-db-between-services"]} />
 
 ## Structure services using sub-packages
 

docs/develop/testing.md

@@ -70,7 +70,7 @@ against that database. When you later call `et.NewTestDatabase`, Encore creates
 
 ### Service Structs
 
-In tests, [service structs](/docs/primitives/service-structs) are initialized on demand when the first
+In tests, [service structs](/docs/primitives/services-and-apis/service-structs) are initialized on demand when the first
 API call is made to that service and then that instance of the service struct for all future tests. This means your tests
 can run faster as they don't have to each initialize all the service struct's each time a new test starts.
 

docs/go/overview.md

@@ -47,13 +47,13 @@ Using Encore.go to declare infrastructure in application code helps unlock these
 - **No manual configuration required**: No need for Infrastructure-as-Code. Your code is the single source of truth.
 - **Unified codebase**: One codebase for all environments; local, preview, and cloud.
 - **Cloud-agnostic by default**: Encore.go provides an abstraction layer on top of the cloud provider's APIs, so you avoid becoming locked in to a single cloud.
-- **Evolve infrastructure without code changes**: As requirements evolve, you can change the provisioned infrastructure without making code changes, either using the Open Source [self-hosting tools](/docs/deploy/self-hosting) or fully-automated in your AWS/GCP account using [Encore's Cloud Platform](https://encore.dev/use-cases/devops-automation).
+- **Evolve infrastructure without code changes**: As requirements evolve, you can change the provisioned infrastructure without making code changes, either using the Open Source [self-hosting tools](/docs/how-to/self-host) or fully-automated in your AWS/GCP account using [Encore's Cloud Platform](https://encore.dev/use-cases/devops-automation).
 cloud provider's console.
 
 ## No DevOps experience required
 
 Encore provides open source tools to help you integrate with your cloud infrastructure, enabling you to self-host your application anywhere to supports Docker containers.
-Learn more in the [self-host documentation](/docs/deploy/self-hosting).
+Learn more in the [self-host documentation](/docs/how-to/self-host).
 
 You can also use [Encore's Cloud Platform](https://encore.dev/use-cases/devops-automation), which fully automates provisioning and managing infrastructure in your own cloud on AWS and GCP.
 

docs/ts/concepts/benefits.md

@@ -13,7 +13,7 @@ lang: ts
 - **No manual configuration required**: No need for Infrastructure-as-Code. Your code is the single source of truth.
 - **Unified codebase**: One codebase for all environments; local, preview, and cloud.
 - **Cloud-agnostic by default**: Encore.ts provides an abstraction layer on top of the cloud provider's APIs, so you avoid becoming locked in to a single cloud.
-- **Evolve infrastructure without code changes**: As requirements evolve, you can change the provisioned infrastructure without needing application code changes. Either using the Open Source [self-hosting tools](/docs/deploy/self-hosting) or with the optional [Cloud Platform](https://encore.dev/use-cases/devops-automation), which fully-automates infrastructure management in your own AWS/GCP account.
+- **Evolve infrastructure without code changes**: As requirements evolve, you can change the provisioned infrastructure without needing application code changes. Either using the Open Source [self-hosting tools](/docs/how-to/self-host) or with the optional [Cloud Platform](https://encore.dev/use-cases/devops-automation), which fully-automates infrastructure management in your own AWS/GCP account.
 
 ## High-performance Rust runtime
 
@@ -53,7 +53,7 @@ Encore leverages static code analysis to parse the API schema and TypeScript typ
 ## No DevOps experience required
 
 Encore provides open source tools to help you integrate with your cloud infrastructure, enabling you to self-host your application anywhere that supports Docker containers.
-Learn more in the [self-host documentation](/docs/deploy/self-hosting).
+Learn more in the [self-host documentation](/docs/how-to/self-host).
 
 You can also use [Encore's Cloud Platform](https://encore.dev/use-cases/devops-automation), which fully automates provisioning and managing infrastructure in your own cloud on AWS and GCP.
 

docs/tutorials/graphql.mdx

@@ -481,7 +481,7 @@ export const add = api(
 );
 ```
 
-The `book` service contains two endpoint, one for listing all books and another to add a new book to the database. Our "database" is hardcoded just to limit the scope of this example. Take a look at the [Using SQL databases](docs/ts/primitives/databases) docs to learn how to set up and use a database.
+The `book` service contains two endpoint, one for listing all books and another to add a new book to the database. Our "database" is hardcoded just to limit the scope of this example. Take a look at the [Using SQL databases](/docs/ts/primitives/databases) docs to learn how to set up and use a database.
 
 We get the `Book` type from the generated resolver types. This will make it easier later when we create the resolver functions.