[#58] pre-link MFM content (#59)

[akkoma] / docs / installation / migrating_to_akkoma.md

diff --git a/docs/installation/migrating_to_akkoma.md b/docs/installation/migrating_to_akkoma.md
index a6b0fc0c26a66e169d21046d1be307d5d29783f7..698e054f1d1fbe8fd06fcc81c3d950d49769f66a 100644 (file)
--- a/docs/installation/migrating_to_akkoma.md
+++ b/docs/installation/migrating_to_akkoma.md
@@ -1,10 +1,11 @@
 # Migrating to Akkoma
 
-**Akkoma does not currently have a stable release, until 3.0, all builds should be considered "develop**
+**Akkoma does not currently have a stable release, until 3.0, all builds should be considered "develop"**
 
 ## Why should you migrate?
 
-aside from actually responsive maintainer(s)? let's lookie here, we've got
+aside from actually responsive maintainer(s)? let's lookie here, we've got:
+
 - custom emoji reactions
 - misskey markdown (MFM) rendering and posting support
 - elasticsearch support (because pleroma search is GARBAGE)
@@ -15,14 +16,14 @@ aside from actually responsive maintainer(s)? let's lookie here, we've got
 ## Actually migrating
 
 Let's say you're very cool and have decided to move to the cooler
-fork of Pleroma - luckily this isn't very hard.
+fork of Akkoma - luckily this isn't very hard.
 
 You'll need to update the backend, then possibly the frontend, depending
 on your setup.
 
 ## From Source
 
-If you're running the source Pleroma install, you'll need to set the
+If you're running the source Akkoma install, you'll need to set the
 upstream git URL then just rebuild - that'll be:
 
 ```bash