From c0d94b2de7af5ebbf9d31986ac3362c29b9c3df7 Mon Sep 17 00:00:00 2001
From: "Sam G." <samgriesemer@gmail.com>
Date: Sun, 11 Aug 2024 05:18:47 -0700
Subject: [PATCH] fix README tag issue

---
 README.md         | 2 +-
 symconf/config.py | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index a23b08b..59cb457 100644
--- a/README.md
+++ b/README.md
@@ -10,7 +10,7 @@ Below is a simple example demonstrating two system-wide theme switches:
 
 This GIF shows two `symconf` calls, the first of which applies a `gruvbox` dark theme and
 the second a dark [`monobiome`][1] variant. Each call (of the form `symconf config -m dark -s
-<style>`) indicates a dark mode preference and a particular color palette that should be
+style`) indicates a dark mode preference and a particular color palette that should be
 used when populating config file templates. Specifically, in this example, invoking
 `symconf` results in the following app-specific config updates:
 
diff --git a/symconf/config.py b/symconf/config.py
index 353a1d8..b5276e0 100644
--- a/symconf/config.py
+++ b/symconf/config.py
@@ -544,7 +544,7 @@ class ConfigManager:
             2. Get matching user config files via ``get_matching_configs()``
             3. Get matching template config files and the aggregate template dict via
                ``get_matching_templates()``
-            4. Interleave the two the result sets by pathname and match quality. Template
+            4. Interleave the two result sets by pathname and match quality. Template
                matches are preferred in the case of tied scores. This resolves any
                pathname clashes across matching files.