diff --git a/.github/workflows/main.yaml b/.github/workflows/main.yaml
index 2082582..4983371 100644
--- a/.github/workflows/main.yaml
+++ b/.github/workflows/main.yaml
@@ -28,7 +28,7 @@ jobs:
         with:
           allowUpdates: true
           name: Release ${{ steps.get-version.outputs.version }}
-          draft: true
+          draft: false
           prerelease: false
           token: ${{secrets.GITHUB_TOKEN}}
           artifacts: './module.zip, ./src/lock-the-sheets/module.json'
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 8517b16..6d50264 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,2 +1,2 @@
 ## 1.0.0
-### 2024-??-?? - Going out into the world!
+### 2023-12-18 - Into the great wide open (initial release)
diff --git a/README.md b/README.md
index 62b2bfa..ebc0763 100644
--- a/README.md
+++ b/README.md
@@ -52,11 +52,11 @@ In **default settings**, lock status is indicated by overlay icons, both in the
 
 ![](src/lock-the-sheets/artwork/lock-the-sheets-readme-combat.png)
 
-Let's see, what happens if players try to **manipulate their hitpoints:**
+Let's see what happens if players try to **manipulate their hitpoints:**
 
 ![](src/lock-the-sheets/artwork/lock-the-sheets-readme-blocked-action-1.png)
 
-But as we said that this is not about cheating prevention in the first place, let's see what happens if a player accidentally happens to **delete an inventory item:**
+But apart from cheating prevention, let's see what happens if a player **accidentally** happens to **delete an inventory item:**
 
 ![](src/lock-the-sheets/artwork/lock-the-sheets-readme-blocked-action-2.png)