@@ -45,8 +45,8 @@ best format, as it can simply be turned into
4545HTML. And as we know, when it's HTML format, that's
4646the very consumption of web browsers, isn't it?
4747
48- Now, here is the catch, when you want to distribute
49- your content as in it's hard copy,
48+ Now, here is the catch: when you want to distribute
49+ your content as hard copy,
5050in Google Chrome, you can simply
5151right-click the page and click ` Print `
5252you now have the PDF version of your content.
@@ -55,7 +55,14 @@ website, you can simply embed the page and
5555you're job is done. You have the repo as the
5656active site for its development, maybe, others
5757will collaborate too, and then the GitHub Page
58- as the output.
58+ as the output. If ever you need a Google Docs
59+ or Microsoft Word
60+ versions of this, simply copy the rendered
61+ markdown file of GitHub and paste it
62+ on Google Docs or Microsoft Word, the format
63+ will still be correct.
64+
65+ As you can see, it's very practical.
5966
6067## How To
6168In the same way you keep your pages and assets in one
0 commit comments