docs: add claude.md and avoid dashes

packaging/README.md

@@ -1,7 +1,7 @@
 # Packaging and releases
 
 The Makefile installs everything; these only wrap what it produced. That is
-deliberate — a packaging script that lists the files again is a second
+on purpose: a packaging script that lists the files again is a second
 description of the layout, and two descriptions drift.
 
 | | |
@@ -44,14 +44,14 @@ gh workflow run release.yml -f dry_run=true
 
 Builds both packages, builds both repositories with a key generated on the
 spot, checks the three signatures it wrote, and then installs the packages back
-out of the repositories — apt on the runner, dnf in a Fedora container. Nothing
+out of the repositories (apt on the runner, dnf in a Fedora container). Nothing
 is pushed and no release is made. This is worth running after any change to the
 packaging, because the alternative is finding out from a tag.
 
 ## Setting up the signing, once
 
 The repositories are signed, so this needs a key. Make one that exists for
-nothing else — not a personal key — and give it no passphrase: it lives as an
+nothing else (not a personal key) and give it no passphrase. It lives as an
 encrypted repository secret, and `rpmsign` cannot be handed a passphrase
 unattended.
 
@@ -66,7 +66,7 @@ gpg --armor --export-secret-keys 'middleclick-autoscroll repository' \
 Without the secret the workflow still builds both packages and attaches them to
 the release; it says so in the log and leaves the repositories alone.
 
-## Pointing Pages at it, once — and in this order
+## Pointing Pages at it, once, in this order
 
 The `gh-pages` branch does not exist until a release has put something on it,
 and a branch that does not exist cannot be picked in the Pages settings. So:
@@ -77,8 +77,8 @@ and a branch that does not exist cannot be picked in the Pages settings. So:
    root.
 
 Doing it the other way round is a wall, and leaving Pages pointed at `main`
-serves the source tree at the address the install instructions name — the key
-and the indexes are 404 and nothing installs.
+serves the source tree at the address the install instructions name. Then the
+key and the indexes are 404 and nothing installs.
 
 ## What users end up with
 

packaging/build-deb.sh

@@ -5,7 +5,7 @@
 #
 # Everything the package contains comes out of `make install`. This only wraps
 # what that produced, so there is exactly one description of where a file goes
-# and it is the Makefile - a packaging script that lists the files again is a
+# and it is the Makefile. A packaging script that lists the files again is a
 # second description, and the two drift.
 #
 # Needs: make, dpkg-deb, msgfmt (gettext), scdoc.

packaging/check-version.sh

@@ -3,12 +3,12 @@
 # Refuses a release whose tag and Makefile disagree.
 #
 # The version is baked into the program at install time from the Makefile, and
-# the packages take theirs from the same place - but the tag is what people see
+# the packages take theirs from the same place. But the tag is what people see
 # and what the release is named after. A tag that says something else produces
 # a package called 1.0.4 containing a program that reports 1.0.3, and nothing
 # would have complained.
 #
-# Anything that is not a v-tag - a run started by hand from a branch - is not a
+# Anything that is not a v-tag (a run started by hand from a branch) is not a
 # release and has nothing to check.
 
 set -euo pipefail
@@ -19,7 +19,7 @@ ref="${1:-}"
 case "$ref" in
 	v[0-9]*) ;;
 	*)
-		echo "not a release tag (${ref:-none}) - nothing to check against"
+		echo "not a release tag (${ref:-none}), nothing to check against"
 		exit 0
 		;;
 esac

packaging/deb/control

@@ -8,7 +8,7 @@ Depends: bash (>= 4.2), coreutils, findutils, grep, sed, mawk | gawk | original-
 Recommends: gettext-base, systemd, desktop-file-utils
 Homepage: https://github.com/LoonixTools/middleclick-autoscroll
 Description: middle-click autoscroll for Chromium-based applications
- Blink - the engine inside Chromium, Electron and CEF - has had Windows-style
+ Blink (the engine inside Chromium, Electron and CEF) has had Windows-style
  autoscroll for years: hold the middle mouse button, move the pointer, the page
  scrolls. On Linux it is switched off, because middle click is already taken by
  primary-selection paste.

packaging/pages/index.html

@@ -64,9 +64,9 @@
 
 <h1>middleclick-autoscroll</h1>
 <p class="lead">
-  Middle-click autoscroll — hold the middle mouse button, move the pointer, the
-  page scrolls — in every Chromium-based application on the system, and in
-  anything installed later.
+  Middle-click autoscroll in every Chromium-based application on the system,
+  and in anything installed later: hold the middle mouse button, move the
+  pointer, and the page scrolls.
 </p>
 
 <p>
@@ -103,7 +103,7 @@ sudo zypper install middleclick-autoscroll</code></pre>
 <p>
   That is the whole setup. Nothing else has to be configured and no file has to
   be edited. Run <code>middleclick-autoscroll disable</code> before removing the
-  package — it puts back everything that was changed.
+  package. It puts back everything that was changed.
 </p>
 
 <footer>

packaging/publish-repos.sh

@@ -11,7 +11,7 @@
 # Usage: publish-repos.sh <gh-pages checkout> <directory of new packages>
 #
 # Needs: dpkg-dev, apt-utils, createrepo-c, gpg, and a secret key already
-# imported - its id is taken from the keyring.
+# imported. Its id is taken from the keyring.
 
 set -euo pipefail
 

packaging/rpm/middleclick-autoscroll.spec

@@ -33,7 +33,7 @@ Recommends:     systemd
 Recommends:     desktop-file-utils
 
 %description
-Blink - the engine inside Chromium, Electron and CEF - has had Windows-style
+Blink (the engine inside Chromium, Electron and CEF) has had Windows-style
 autoscroll for years: hold the middle mouse button, move the pointer, the page
 scrolls. On Linux it is switched off, because middle click is already taken by
 primary-selection paste.