David Else

@the-mikedavis It is done! I made your suggested changes, and re-read the entire thing and made a few more corrections/changes. If you and @archseer are happy with them we are...

@archseer This has been my first time responding to a GitHub code review, should I always reply to suggestions or just hit resolved when I have completed them? I have...

I have now done everything in the code reviews, anything more I need to do?

We don't need this! GitHub has a special mode to review diffs for Markdown :) https://docs.github.com/en/repositories/working-with-files/using-files/working-with-non-code-files#rendering-differences-in-prose-documents

It seems this fix might be preferable to GitHub prose diff mode. You can get the same results with the following, making sure the `.prettierrc` is in `book/src`: `.prettierrc` ```...

@thomkeh Thanks for that link. I did't think it would be a good idea in this situation as GitHub has automatic prose diff rendering that takes care of line break...

@the-mikedavis Thanks for the update. I am in a bit of a limbo here, I need some feedback on the work I have done on the documentation before continuing, but...

@the-mikedavis I am quite new to advanced Git and don't really understand what force pushing to my branch in GitHub would mean, would that result with a new commit from...

@pascalkuthe I see you are looking at the LSP at the moment with https://github.com/helix-editor/helix/pull/5711 , can you do anything about this issue? In my experience replace behaves more like a...

It is done and released in deno 1.2 :) https://github.com/denoland/deno/pull/6372