diff --git a/content/200-orm/500-reference/300-environment-variables-reference.mdx b/content/200-orm/500-reference/300-environment-variables-reference.mdx
index 407c6bf4fe..271e327e89 100644
--- a/content/200-orm/500-reference/300-environment-variables-reference.mdx
+++ b/content/200-orm/500-reference/300-environment-variables-reference.mdx
@@ -167,7 +167,7 @@ This environment variable is available since version `4.16.0`
 
 </Admonition>
 
-`PRISMA_ENGINES_CHECKSUM_IGNORE_MISSING` can be can be set to a truthy value to ignore problems around downloading & verifying the integrity (via a checksum file) of the Prisma ORM engines.
+`PRISMA_ENGINES_CHECKSUM_IGNORE_MISSING` can be set to a truthy value to ignore problems around downloading & verifying the integrity (via a checksum file) of the Prisma ORM engines.
 This is particularly useful when deploying to an offline system environment where the checksum file cannot be downloaded.
 
 ```env
@@ -192,7 +192,7 @@ PRISMA_QUERY_ENGINE_BINARY=custom/query-engine-<target>
 For Prisma CLI it allows you to define the query engine file to be used.  
 For Prisma Client, on build time (during `prisma generate`), it defines where the query engine file will be copied from into Prisma Client. At run time (when using the generated Client) it can be used to define the specific query engine file to be used instead of the included one.
 
-Note: This can only have an effect if the engine type of CLI or Client are set to `binary`. If the engine type is `library` (the default), use PRISMA_QUERY_ENGINE_LIBARY instead.
+Note: This can only have an effect if the engine type of CLI or Client are set to `binary`. If the engine type is `library` (the default), use PRISMA_QUERY_ENGINE_LIBRARY instead.
 
 #### `PRISMA_QUERY_ENGINE_LIBRARY`