aboutsummaryrefslogtreecommitdiff
path: root/content/blog
diff options
context:
space:
mode:
authorChristian Cleberg <[email protected]>2026-08-11 16:22:19 -0500
committerChristian Cleberg <[email protected]>2026-08-11 20:35:15 -0500
commit87068dcdb9fa279e6fe620ecb4086f157090a0d0 (patch)
treed4b6ba2f2b2532b1318051e53d523b59dcbe6bf7 /content/blog
parent92706a3264ffc4562066ef98e0b2bf4a3a9dcb45 (diff)
downloadcleberg.net-87068dcdb9fa279e6fe620ecb4086f157090a0d0.tar.gz
cleberg.net-87068dcdb9fa279e6fe620ecb4086f157090a0d0.tar.bz2
cleberg.net-87068dcdb9fa279e6fe620ecb4086f157090a0d0.zip
Close the space before the full stop
The link's closing brackets were followed by a space, so the sentence ended "through time ." on the page. Left over from removing something, most likely. No others like it in the corpus.
Diffstat (limited to 'content/blog')
-rw-r--r--content/blog/2021-04-23-php-comment-system.org2
1 files changed, 1 insertions, 1 deletions
diff --git a/content/blog/2021-04-23-php-comment-system.org b/content/blog/2021-04-23-php-comment-system.org
index f2b49de..5baf04a 100644
--- a/content/blog/2021-04-23-php-comment-system.org
+++ b/content/blog/2021-04-23-php-comment-system.org
@@ -44,7 +44,7 @@ it turns out, this was a perfect solution for me.
The second issue for my personal use-case is that I am trying to keep the
contents of my website accessible over time, as described by Brandur,
in his post entitled [[https://brandur.org/fragments/graceful-degradation-time][Blog with Markdown + Git, and degrade gracefully through
-time]] .
+time]].
This means I cannot rely on a database for comments, since I do not rely on a
database for any other part of my websites.