minor docs changes

3 files changed, 2 insertions, 5 deletions

diff --git a/Sources/bar/bar.docc/how-it-works.md b/Sources/bar/bar.docc/how-it-works.md
index 1ab5753..ab8216a 100644
--- a/Sources/bar/bar.docc/how-it-works.md
+++ b/Sources/bar/bar.docc/how-it-works.md
@@ -25,8 +25,7 @@ The way to install *bar* is simply to download or clone the repository on your s
 
 ## How to extend the functionality
 
-*bar* already does a lot out of the box, but it is deliberately more limited compared to other solutions like [SketchyBar](https://felixkratz.github.io/SketchyBar/).
-What if you need a specific feature that is not available?
+*bar* already works very well out of the box, but what if you need a specific feature that is not available?
 Well, you can build it or patch it yourself.
 
 *bar* aims to stay focused and minimal, so it can be read through and understood in roughly an hour.
diff --git a/Sources/bar/bar.docc/installation.md b/Sources/bar/bar.docc/installation.md
index 6475aa1..bee3dfd 100644
--- a/Sources/bar/bar.docc/installation.md
+++ b/Sources/bar/bar.docc/installation.md
@@ -42,5 +42,5 @@ If you don't have `make`, build directly with the Swift Package Manager:
 
 ```shell
 swift build -c release
-cp .build/release/bar /usr/local/bin/
+cp .build/release/bar ~/.local/bin/
 ```
diff --git a/Sources/bar/bar.docc/patches.md b/Sources/bar/bar.docc/patches.md
index c4f02e3..c173ba5 100644
--- a/Sources/bar/bar.docc/patches.md
+++ b/Sources/bar/bar.docc/patches.md
@@ -43,8 +43,6 @@ For example:
 git diff > my-awesome-feature.patch
 ```
 
-If you want to submit the patch to the community, upload it somewhere publicly accessible (e.g., a GitHub repo or a personal website) and link it in the patch documentation.
-
 > Important: A good patch is focused on a single feature and does not include unrelated changes.
 > This makes it easier for others to review and apply only what they need.