diff --git a/doc/git-annex-unlock.mdwn b/doc/git-annex-unlock.mdwn
index 1a2bd32596..6d0ad22a7a 100644
--- a/doc/git-annex-unlock.mdwn
+++ b/doc/git-annex-unlock.mdwn
@@ -39,9 +39,10 @@ repository. So, enable annex.thin with care.
 
 	# git annex unlock photo.jpg
 	# gimp photo.jpg
-	# git annex add photo.jpg
-	# git annex lock photo.jpg
-	# git commit -m "redeye removal"
+	# git commit photo.jpg -m "redeye removal"
+	# gimp photo.jpg
+	# git commit photo.jpg -m "fix oversaturation"
+    # git annex lock photo.jpg
 
 # OPTIONS
 
diff --git a/doc/git-annex-unlock/comment_13_db3d6eb5f238edbd505b6909863167df._comment b/doc/git-annex-unlock/comment_13_db3d6eb5f238edbd505b6909863167df._comment
new file mode 100644
index 0000000000..777bcdf187
--- /dev/null
+++ b/doc/git-annex-unlock/comment_13_db3d6eb5f238edbd505b6909863167df._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""Re: We don’t need a 'git annex lock' after a 'git annex add', right?"""
+ date="2025-09-16T17:28:49Z"
+ content="""
+Well spotted. `git-annex add` defaults to adding files locked, even when
+adding what was an unlocked file before.
+
+I've improved the example.
+"""]]