From dc7299eb2f7d620aedd2667af73fa16aa35c54a2 Mon Sep 17 00:00:00 2001
From: David Wolf <68775926+devidw@users.noreply.github.com>
Date: Tue, 18 Oct 2022 12:37:15 +0200
Subject: [PATCH] Add leading `v` to ver number in env docs (#14608)

Other version string have the `v`, this one doesn't, this way it's equal in the block

Co-authored-by: Usha Mandya <47779042+usha-mandya@users.noreply.github.com>
---
 compose/environment-variables.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/compose/environment-variables.md b/compose/environment-variables.md
index 0b3af89697..d71c2da6a2 100644
--- a/compose/environment-variables.md
+++ b/compose/environment-variables.md
@@ -35,7 +35,7 @@ named `.env`. The `.env` file path is as follows:
 
   - Starting from `v1.28`, the `.env` file is placed at the base of the project directory.
   - Project directory can be explicitly defined with the `--file` option or `COMPOSE_FILE`
-  environment variable. Otherwise, it is the current working directory where the `docker compose` command is executed (`+1.28`).
+  environment variable. Otherwise, it is the current working directory where the `docker compose` command is executed (`v1.28`).
   - For versions older than `v1.28`, it might have trouble resolving `.env` file with `--file` or `COMPOSE_FILE`. To work around it, it is recommended to use `--project-directory`, which overrides the path for the `.env` file. This inconsistency is addressed in `v1.28` by limiting the file path to the project directory.