From 7494706e881ff5b555cc859f2ef9f996ea6d6c67 Mon Sep 17 00:00:00 2001
From: Sergey A <7361274+murlakatamenka@users.noreply.github.com>
Date: Mon, 16 Jan 2023 16:37:21 +0300
Subject: [PATCH] Fix minor inconsistency

---
 Setting-Environmental-Variables.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Setting-Environmental-Variables.md b/Setting-Environmental-Variables.md
index 860201f..70680e4 100644
--- a/Setting-Environmental-Variables.md
+++ b/Setting-Environmental-Variables.md
@@ -34,7 +34,7 @@ Technically, you could set them in your sway config.
 <!-- er... mind explaining how, or giving an example? -AtlasC0R3 -->
 
 ## Login Shell
-If you launch sway from my login shell, your ~/.zprofile or ~/.profile should work.
+If you launch sway from your login shell, your ~/.zprofile or ~/.profile should work.
 
 ## User Service
 You can set variables using the environment.d. Environment variables set there will be read by the --user systemd, and since everything is started in its hierarchy variables will properly propagate.