From 788462ef93edbf9c72c8420d3a10c874dc364a8e Mon Sep 17 00:00:00 2001
From: Alex Ruheni <aleruheni@outlook.com>
Date: Wed, 8 Feb 2023 10:20:29 +0100
Subject: [PATCH] chore: update env var references

---
 .../300-environment-variables-reference.mdx               | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/content/400-reference/200-api-reference/300-environment-variables-reference.mdx b/content/400-reference/200-api-reference/300-environment-variables-reference.mdx
index 429d46c550..2b0ceb3608 100644
--- a/content/400-reference/200-api-reference/300-environment-variables-reference.mdx
+++ b/content/400-reference/200-api-reference/300-environment-variables-reference.mdx
@@ -186,7 +186,11 @@ PRISMA_MIGRATION_ENGINE_BINARY=custom/my-migration-engine-unix
 PRISMA_INTROSPECTION_ENGINE_BINARY=custom/my-introspection-engine-unix
 ```
 
-### CLI Binary Targets
+<Admonition type="warning">
+
+- The Introspection Engine is served by the Migration Engine from [4.9.0](https://github.com/prisma/prisma/releases/tag/4.9.0). Therefore, the `PRISMA_INTROSPECTION_ENGINE` environment variable will not be used.
+
+</Admonition>
 
 #### <inlinecode>PRISMA_FMT_BINARY</inlinecode>
 
@@ -202,6 +206,8 @@ The `PRISMA_FMT_BINARY` variable is used in versions [4.2.0](https://github.com/
 
 </Admonition>
 
+### CLI Binary Targets
+
 #### <inlinecode>PRISMA_CLI_BINARY_TARGETS</inlinecode>
 
 `PRISMA_CLI_BINARY_TARGETS` can be used to specify one or more binary targets that Prisma CLI will download during installation (so it must be provided during `npm install` of Prisma CLI and does not affect runtime of Prisma CLI or Prisma Client).