refactor: 📝 explain about release process more in CHANGELOG (#132)

# Description

Just a bit more detail about how the releases work.

Closes #106

Needs a quick review.

## Checklist

- [x] Formatted Markdown
- [x] Ran `just run-all`

---------

Co-authored-by: Signe Kirk Brødbæk <signebroedbaek@gmail.com>
Co-authored-by: Joel Ostblom <joelostblom@users.noreply.github.com>

Author: 3 people

CHANGELOG.md

@@ -2,12 +2,18 @@
 
 Since we follow [Conventional
 Commits](https://decisions.seedcase-project.org/why-conventional-commits),
-we're able to automatically create a release with
+we're able to automatically create formal "releases" of the website
+based on our commit messages. Releases in the context of websites are
+simply snapshots in time of the website content. We use
 [Commitizen](https://decisions.seedcase-project.org/why-semantic-release-with-commitizen)
-based on the commit messages. This means that releases can happen quite
-often, sometimes several in a day. It also means any individual release
-will not have many changes within it. Below is a list of releases along
-with what was changed within it.
+to automatically create these releases using
+[SemVer](https://semverdoc.org) as the version numbering scheme.
+
+Because releases are created based on commit messages, a new release is
+created quite often---sometimes several times in a day. This also means
+that any individual release will not have many changes within it. Below
+is a list of the releases we've made so far, along with what was changed
+within each release.
 
 ## 0.17.9 (2025-11-07)
 

template/CHANGELOG.md

@@ -2,9 +2,15 @@
 
 Since we follow [Conventional
 Commits](https://decisions.seedcase-project.org/why-conventional-commits),
-we're able to automatically create a release with
+we're able to automatically create formal "releases" of the website
+based on our commit messages. Releases in the context of websites are
+simply snapshots in time of the website content. We use
 [Commitizen](https://decisions.seedcase-project.org/why-semantic-release-with-commitizen)
-based on the commit messages. This means that releases can happen quite
-often, sometimes several in a day. It also means any individual release
-will not have many changes within it. Below is a list of releases along
-with what was changed within it.
+to automatically create these releases using
+[SemVer](https://semverdoc.org) as the version numbering scheme.
+
+Because releases are created based on commit messages, a new release is
+created quite often---sometimes several times in a day. This also means
+that any individual release will not have many changes within it. Below
+is a list of the releases we've made so far, along with what was changed
+within each release.