summaryrefslogtreecommitdiff
path: root/mds/blog/converting-form-mds.md
diff options
context:
space:
mode:
Diffstat (limited to 'mds/blog/converting-form-mds.md')
-rw-r--r--mds/blog/converting-form-mds.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/mds/blog/converting-form-mds.md b/mds/blog/converting-form-mds.md
index ee5e6a8..b1847bb 100644
--- a/mds/blog/converting-form-mds.md
+++ b/mds/blog/converting-form-mds.md
@@ -79,7 +79,7 @@ links interfering with the text.
<figure>
> Like Gopher (and unlike Markdown or HTML), Gemtext only lets you put links to other documents on a line of their own. You can't make a single word in the middle of a sentence into a link. This takes a little getting used to, but it means that links are extremely easy to find, and clients can style them differently (e.g. to make it clear which protocol they use, or to display the domain name to help users decide whether they want to follow them or not) without interfering with the readability of your actual textual content.
-<figcaption>--- <cite>[gemini.circumlunar.space -- A quite introduction to "gemtext" markup | Links](https://gemini.circumlunar.space/docs/gemtext.gmi)</cite></figcaption>
+<figcaption>--- <cite>[gemini.circumlunar.space -- A quick introduction to "gemtext" markup | Links](https://gemini.circumlunar.space/docs/gemtext.gmi)</cite></figcaption>
</figure>
I felt that this provided a lot of useful limitations that removed a huge barrier for me to actually write down ideas without feeling over burdened. I also lurked in the IRC - as well as [implemented my own gemini server](https://github.com/s3nd3r5/java-gemini-server).