From 92adc0503bd60bac60cc00ea7677054b181da493 Mon Sep 17 00:00:00 2001
From: David Karlsson <35727626+dvdksn@users.noreply.github.com>
Date: Tue, 8 Nov 2022 15:11:33 +0100
Subject: [PATCH] fix typo in compose envvars (#16118)

---
 compose/envvars-precedence.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/compose/envvars-precedence.md b/compose/envvars-precedence.md
index 4a0517ffb1..97449ecc72 100644
--- a/compose/envvars-precedence.md
+++ b/compose/envvars-precedence.md
@@ -4,7 +4,7 @@ description: Scenario Overview illustrating how environment variables are resolv
 keywords: compose, environment, env file
 ---
 
-This page contains information on how how interpolation works when using environment variables in Compose.
+This page contains information on how interpolation works when using environment variables in Compose.
 
 When you set the same environment variable in multiple files, there’s a precedence rule used by Compose. It aims to resolve the value for the variable in question. 
 
@@ -57,4 +57,4 @@ Each row represents a combination of contexts where `TAG` is set or passed simul
 
 > **Note**
 >
-> The columns _`Host OS` environment_ and _`.env` file_ is listed only for lookup. These columns can't result in a variable in the container by itself.
\ No newline at end of file
+> The columns _`Host OS` environment_ and _`.env` file_ is listed only for lookup. These columns can't result in a variable in the container by itself.