diff --git a/content/posts/neorg.md b/content/posts/neorg.md
index b3fc6a7..642311b 100644
--- a/content/posts/neorg.md
+++ b/content/posts/neorg.md
@@ -15,17 +15,17 @@ well with the new rewrite.
 Don't get me wrong, the default neorg experience is actually amazing and the syntax is clearly (subjectively) superior
 to regular emacs org-mode, but I'm not sure if either of those can compete with the increasingly standardized markdown
 syntax. In any case, when you are trusting your most personal inner thoughts with a syntax, you should really strive
-to use something that has (Neorg actually fails in both of these points):
+to use something that has:
 
 1. Survived the bathtub curve, and
 2. Won't lock you down to a specific tool.
 
-The second point is probably the most important one. A general life-advise that I first heard from Luke Smith is that
-whenever you have a life decision to make, you should favor the choice that maximises your personal freedom. i.e. If
-one of the choices limit you to only being able to do a thing in one way, using only one tool, provided, managed and
-maintained by one entity (company or person) and the other enables you to do the thing however you want. Or at least
-you can do the thing in multiple ways. You should strongly prefer the second option - even if it's a bit less
-convenient and less sleek or sexy.
+Neorg actually fails in both of these points.
+The second point is probably the most important one. A general life-advise is that whenever you have a life decision to
+make, you should favor the choice that maximises your personal freedom. i.e. If one of the choices limit you to only
+being able to do a thing in one way, using only one tool, provided, managed and maintained by one entity (company or
+person) and the other enables you to do the thing however you want. Or at least you can do the thing in multiple ways.
+You should strongly prefer the second option - even if it's a bit less convenient and less sleek or sexy.
 
 We got a bit off track there. Let's get back to how to migrate away from Neorg. I have a couple of criteria for such a
 tool that I need.
@@ -40,8 +40,8 @@ Finding such programs is a separate tools-search though, and should be done base
 - Folding (`set foldmethod=expr` see [https://www.jmaguire.tech/posts/treesitter_folding/](https://www.jmaguire.tech/posts/treesitter_folding/))
 - Quickly marking checklists as done (e.g. `<C-space>` or `<leader>td`)
 - Standardized syntax that is widely used
-- Pressing `<Return>` to follow links (create if not exists)
-- `image.nvim` support - preferably through `snacks.nvim`
+- Easy way to follow links (create if not exists)
+- `image.nvim` support
 
 ## Markdown
 
@@ -49,11 +49,10 @@ Just raw markdown might be the way to go. I can set `conceallevel=2` for prettie
 a couple of things that I want that I might need to mold out using custom things.
 - Follow links: [https://github.com/jghauser/follow-md-links.nvim](https://github.com/jghauser/follow-md-links.nvim)
 
-
 ### Converting from Neorg
 
 Neorg have an integrated markdown exporter which works fairly okay. It gets links a bit messed up - especially if it
-is a link to [another neorg file](#indexmd).
+is a link to [another neorg file](#indexmd), and there tends to be way too much whitespace. This is manageble though.
 
 ## Vimwiki
 
@@ -79,8 +78,8 @@ vim.g.vimwiki_global_ext = 0
 
 ### Converting from Neorg
 
-If using markdown as the vimwiki syntax, it should be the same procedure as [Markdown](#markdown). Otherwise, `pandoc` can
-probably get you there if you use markdown as a middle-step.
+If using markdown as the vimwiki syntax, it should be the same procedure as [Markdown](#markdown). Otherwise, `pandoc`
+can probably get you there if you use markdown as a middle-step. This is not ideal though.
 
 ## Org-mode
 
@@ -88,15 +87,13 @@ probably get you there if you use markdown as a middle-step.
 
 This is using the traditional org-mode syntax. This used by almost all emacs users, so it'll make it easy to change
 editor to emacs if I ever decide I want that. Neovim is nice and cool, but it's also very new and not even version 1
-yet.
+yet. The good thing is that this is just a personal choice.
 
 ### Converting from Neorg
 
 You can do a two-step conversion from `.norg` to `.markdown` (see [Markdown](#markdown)) to `.org` (see 
 [https://emacs.stackexchange.com/questions/5465/how-to-migrate-markdown-files-to-emacs-org-mode-format](https://emacs.stackexchange.com/questions/5465/how-to-migrate-markdown-files-to-emacs-org-mode-format)).
 
-
 # Conclusion
 
-
 {{< centered image="/6616144.png" >}}