From 57dd7754247297e884f0e2836cb45eab5abf6276 Mon Sep 17 00:00:00 2001
From: Stoppedpuma <58333920+Stoppedpuma@users.noreply.github.com>
Date: Fri, 7 Jun 2024 21:29:21 +0200
Subject: [PATCH] issues - Fix spelling mistakes of AppArmor and Arch Linux

---
 docs/issues.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/issues.md b/docs/issues.md
index 59ccf0ba..d9f28cfe 100644
--- a/docs/issues.md
+++ b/docs/issues.md
@@ -11,7 +11,7 @@ Known bugs are tracked on the meta issue **[#75](https://github.com/roddhjav/app
 
     * `deny` rules are enforced even in complain mode,
     * `attach_disconnected` (and `mediate_deleted`) will break the program if they are required and missing in the profile,
-    * If apparmor does not find the profile to transition `rPx`.
+    * If AppArmor does not find the profile to transition `rPx`.
 
 ### Pacman "could not get current working directory"
 
@@ -25,7 +25,7 @@ error: could not get current working directory
 
 This is **a feature, not a bug!** It can safely be ignored. Pacman tries to get your current directory. You will only get this error when you run pacman in your home directory.
 
-According to the Archlinux guideline, on Archlinux, packages cannot install files under `/home/`. Therefore, the [`pacman`][pacman] profile purposely does not allow access of your home directory.
+According to the Arch Linux guideline, on Arch Linux, packages cannot install files under `/home/`. Therefore, the [`pacman`][pacman] profile purposely does not allow access of your home directory.
 
 This provides a basic protection against some packages (on the AUR) that may have rogue install script.