typo

posts/friction-to-publish.md

@@ -13,7 +13,7 @@ I was having a conversation over email with [Louie Mantia](https://lmnt.me) on t
 
 Most self-hosted publishing products have a fritcion problem when compared to writing on blogging products like Medium or X. For example, when I want to write a new post on this blog, I have to pull out my code editor, create a new Markdown file, write the post, and then push it to the repository. This is a lot of "not writing" when the goal is to write, not to mention that I have to know about Github and use `git` for it all to work.
 
-[Rook](https://github.com/davidhariri/rook) so far is a good solution for people who already understand web applications, blogging and markdown. It's not great for people who just want to write. I think what I need to do now is take a step back and work backwards from the workflow I want to have. I want to, whether I'm on the go or at home, wip out an editor and publish a thought. It should be as easy as posting on Twitter to update my blog, but I want to be able to have the full expressiveness Markdown offers and use a great editor like iA Writer on my iPhone.
+[Rook](https://github.com/davidhariri/rook) so far is a good solution for people who already understand web applications, blogging and markdown. It's not great for people who just want to write. I think what I need to do now is take a step back and work backwards from the workflow I want to have. I want to, whether I'm on the go or at home, whip out an editor and publish a thought. It should be as easy as posting on Twitter to update my blog, but I want to be able to have the full expressiveness Markdown offers and use a great editor like iA Writer on my iPhone.
 
 I think there's an opportunity to build (or adopt..?) a standard protocol that any blog server could implement which would define how a client can list, edit and create posts. We have this for making web requests to APIs, why not for publishing? Perhaps it could define a common standard for commenting and re-sharing?