chore: migrate repository links to reactive-resume/reactive-resume

docs/self-hosting/docker.mdx

@@ -28,7 +28,7 @@ planned. Follow the [Docker Compose quickstart](#quickstart-using-docker-compose
 You can pull the latest app image from:
 
 - Docker Hub: `amruthpillai/reactive-resume:latest`
-- GitHub Container Registry: `ghcr.io/reactive-resume/app:latest`
+- GitHub Container Registry: `ghcr.io/reactive-resume/reactive-resume:latest`
 
 ## Minimum requirements
 
@@ -191,7 +191,7 @@ services:
 
   reactive-resume:
     image: amruthpillai/reactive-resume:latest
-    # image: ghcr.io/reactive-resume/app:latest
+    # image: ghcr.io/reactive-resume/reactive-resume:latest
     restart: unless-stopped
     ports:
       - "3000:3000"
@@ -216,7 +216,7 @@ volumes:
     </CodeGroup>
 
     <Tip>
-      Prefer pulling from Docker Hub? Keep <code>amruthpillai/reactive-resume:latest</code>. Prefer GHCR? Swap it to <code>ghcr.io/reactive-resume/app:latest</code>.
+      Prefer pulling from Docker Hub? Keep <code>amruthpillai/reactive-resume:latest</code>. Prefer GHCR? Swap it to <code>ghcr.io/reactive-resume/reactive-resume:latest</code>.
     </Tip>
 
     <Note>
@@ -254,7 +254,7 @@ docker compose logs -f reactive-resume
 Use your platform's generic container configuration to create two separately managed containers: one for Reactive
 Resume and one for PostgreSQL. No official Unraid Community Applications template is provided.
 
-- Use the official `amruthpillai/reactive-resume:latest` or `ghcr.io/reactive-resume/app:latest` image for the
+- Use the official `amruthpillai/reactive-resume:latest` or `ghcr.io/reactive-resume/reactive-resume:latest` image for the
   app container.
 - Map the app's container port `3000` to the host port you want to use.
 - Connect both containers to a private container network. Set the host in `DATABASE_URL` to the PostgreSQL container or

docs/self-hosting/examples.mdx

@@ -15,7 +15,7 @@ They go further than the basic setup in the [Self-hosting with Docker](/self-hos
 
 <Info>
   **Share your setup.** If you have a working configuration that isn't covered here, I'd love to include it. [Open a
-  pull request](https://github.com/reactive-resume/app) with your example added to this page.
+  pull request](https://github.com/reactive-resume/reactive-resume) with your example added to this page.
 </Info>
 
 ---
@@ -352,7 +352,7 @@ services:
       replicas: 1
 
   reactive_resume:
-    image: ghcr.io/reactive-resume/app:latest
+    image: ghcr.io/reactive-resume/reactive-resume:latest
     networks:
       - traefik_network
       - reactive_resume_network
@@ -457,7 +457,7 @@ Have a different deployment setup that works well? Consider contributing it here
 - Podman configurations
 - Cloud-specific deployments (AWS ECS, Google Cloud Run, Azure Container Apps)
 
-To contribute, [open a pull request](https://github.com/reactive-resume/app) with your example added to this page. Include:
+To contribute, [open a pull request](https://github.com/reactive-resume/reactive-resume) with your example added to this page. Include:
 
 1. A brief description of when/why someone would use this setup
 2. The complete Docker Compose (or equivalent) configuration

docs/self-hosting/migration.mdx

@@ -150,7 +150,7 @@ To run the migration scripts, you need the following installed on your host mach
   <Card title="Reactive Resume Source Code">
     Clone the Reactive Resume repository and check out the last tag that includes the migration scripts:
     ```bash
-    git clone https://github.com/reactive-resume/app.git reactive-resume
+    git clone https://github.com/reactive-resume/reactive-resume.git reactive-resume
     cd reactive-resume
     git checkout tags/v5.0.20
     pnpm install