diff --git a/docs/docs/_partial-gpu-mode-tip.mdx b/docs/docs/_partial-gpu-mode-tip.mdx
index 6a828ef8..d9d229fb 100644
--- a/docs/docs/_partial-gpu-mode-tip.mdx
+++ b/docs/docs/_partial-gpu-mode-tip.mdx
@@ -2,7 +2,4 @@ GPU acceleration isn't required for most use cases.
 OpenRAG's CPU-only deployment doesn't prevent you from using GPU acceleration in external services, such as Ollama servers.
 
 GPU acceleration is required only for specific use cases, typically involving customization of the ingestion flows or ingestion logic.
-For example, writing alternate ingest logic in OpenRAG that uses GPUs directly in the container, or customizing the ingestion flows to use Langflow's Docling component with GPU acceleration instead of OpenRAG's `docling serve` service.
-
-To deploy OpenRAG on an Amazon EC2 instance with GPU acceleration enabled, you must edit the `docker-compose.gpu.yml` file before starting the OpenRAG containers.
-For more information, see [Some images failed to pull on Amazon EC2 with GPU support](/support/troubleshoot#some-images-failed-to-pull-on-amazon-ec2-with-gpu-support).
\ No newline at end of file
+For example, writing alternate ingest logic in OpenRAG that uses GPUs directly in the container, or customizing the ingestion flows to use Langflow's Docling component with GPU acceleration instead of OpenRAG's `docling serve` service.
\ No newline at end of file
diff --git a/docs/docs/support/troubleshoot.mdx b/docs/docs/support/troubleshoot.mdx
index fa1cdaa4..f4d69e6e 100644
--- a/docs/docs/support/troubleshoot.mdx
+++ b/docs/docs/support/troubleshoot.mdx
@@ -35,33 +35,6 @@ open "/Applications/Python VERSION/Install Certificates.command"
 
 Replace `VERSION` with your installed Python version, such as `3.13`.
 
-### Some images failed to pull on Amazon EC2 with GPU support {#some-images-failed-to-pull-on-amazon-ec2-with-gpu-support}
-
-When installing OpenRAG on an Amazon EC2 instance with GPU acceleration enabled, some Docker images might fail to pull.
-
-To resolve this issue, do the following:
-
-1. [Stop the OpenRAG containers](/manage-services#stop-and-start-containers).
-
-2. In your `~/.openrag` directory, edit the `docker-compose.gpu.yml` file as follows:
-
-   ```yaml
-   services:
-   openrag-backend:
-      environment:
-         - NVIDIA_DRIVER_CAPABILITIES=compute,utility
-         - NVIDIA_VISIBLE_DEVICES=all
-      deploy:
-         resources:
-         reservations:
-            devices:
-               - driver: nvidia
-               count: all
-               capabilities: [gpu]
-   ```
-
-3. [Restart the OpenRAG containers](/manage-services#stop-and-start-containers).
-
 ### Application onboarding gets stuck on Google Chrome
 
 If the OpenRAG onboarding process gets stuck when using Google Chrome, try clearing your browser's cache.