diff --git a/content/200-orm/800-more/600-help-and-troubleshooting/100-autocompletion-in-graphql-resolvers-with-js.mdx b/content/200-orm/800-more/600-help-and-troubleshooting/100-autocompletion-in-graphql-resolvers-with-js.mdx
index b0fcd231c4..912ecb7d92 100644
--- a/content/200-orm/800-more/600-help-and-troubleshooting/100-autocompletion-in-graphql-resolvers-with-js.mdx
+++ b/content/200-orm/800-more/600-help-and-troubleshooting/100-autocompletion-in-graphql-resolvers-with-js.mdx
@@ -27,7 +27,7 @@ filterPosts: (parent, args, ctx) => {
 
 Now whenever you type `ctx.` VS Code will provide unnecessary options in the autocomplete which is undesirable.
 
-![Unwanted autocomplete values by VSCode](./unwanted-autocomplete-values-in-vscode.png)
+![Unwanted autocomplete values by VSCode](/img/orm/unwanted-autocomplete-values-in-vscode.png)
 
 VS Code doesn't know the _type_ of the `context` object so it can't provide any intellisense for it, which is why unwanted suggestions are displayed.
 
@@ -69,7 +69,7 @@ This will tell VS Code that the `context` has a property named `prisma` and the
 
 And voilà, autocompletion in plain JavaScript.
 
-![The correct parameters for context are obtained](./prisma-autocompletion-in-js.png)
+![The correct parameters for context are obtained](/img/orm/prisma-autocompletion-in-js.png)
 
 The final file should look something like:
 
diff --git a/content/200-orm/800-more/600-help-and-troubleshooting/600-vercel-caching-issue.mdx b/content/200-orm/800-more/600-help-and-troubleshooting/600-vercel-caching-issue.mdx
index f74a73fbde..5061c15778 100644
--- a/content/200-orm/800-more/600-help-and-troubleshooting/600-vercel-caching-issue.mdx
+++ b/content/200-orm/800-more/600-help-and-troubleshooting/600-vercel-caching-issue.mdx
@@ -96,8 +96,8 @@ Another way to configure `prisma generate` to be run on every deployment is to a
 
 Within your project's dashboard, go to the **Settings** tab and find the **General** section. In that section you will find a box labeled **Build & Development Settings** that contains an input field named **Build Command**:
 
-![Vercel project dashboard's Build Command setting](./vercel-ui-build-command.png)
+![Vercel project dashboard's Build Command setting](/img/orm/vercel-ui-build-command.png)
 
 Within that field, prepend `prisma generate` to the existing script:
 
-![Vercel project dashboard's Build Command setting filled](./vercel-ui-build-command-filled.png)
+![Vercel project dashboard's Build Command setting filled](/img/orm/vercel-ui-build-command-filled.png)
diff --git a/content/200-orm/800-more/600-help-and-troubleshooting/700-netlify-caching-issue.mdx b/content/200-orm/800-more/600-help-and-troubleshooting/700-netlify-caching-issue.mdx
index 41971278c9..663610ef68 100644
--- a/content/200-orm/800-more/600-help-and-troubleshooting/700-netlify-caching-issue.mdx
+++ b/content/200-orm/800-more/600-help-and-troubleshooting/700-netlify-caching-issue.mdx
@@ -98,8 +98,8 @@ Within your project's dashboard, go to the **Site Settings** tab and find the **
 
 Find the box in that section labeled **Build settings** and click the **Edit settings** button:
 
-![Netlify project dashboard's Build settings button](./netlify-edit-settings.png)
+![Netlify project dashboard's Build settings button](/img/orm/netlify-edit-settings.png)
 
 Clicking that button will open a form with various fields. Find the **Build command** field and prepend `prisma generate` to the existing script:
 
-![Netlify project dashboard's Build command setting filled](./netlify-build-command-filled.png)
+![Netlify project dashboard's Build command setting filled](/img/orm/netlify-build-command-filled.png)