Update README.md

MichaelCurrin · web-flow · commit 15f7c7c8ea62 · 2020-05-17T19:20:27.000+02:00
diff --git a/docs/README.md b/docs/README.md
@@ -739,8 +739,12 @@ e.g.
 ```bash
 $ docsify serve docs
 ```
+```
+Serving .../docsify-js-tutorial/docs now.
+Listening at http://localhost:3000
+```
 
-Serves as [localhost:3000/](http://localhost:3000/), or a different port if there is already a _Docsify_ server running.
+Serves at [localhost:3000/](http://localhost:3000/), or a different port if there is already a _Docsify_ server running.
 
 This uses is the main use for Docsify - an `index.html` page is served, the JS is loaded on the frontend and then markdown pages are requested and converted to HTML as needed. It is a **Single-Page Application**, so will work great from a user perspective but will score low on search engines. Even though the SEO crawlers can handle JavaScript, there is limited "crawl budget" for a JavaScript-based SPA so this means less of your site is crawled or your site is rated poorly. Constrast with the option below.
 
@@ -750,6 +754,18 @@ This uses is the main use for Docsify - an `index.html` page is served, the JS i
 
 This command is for Server-Side Rendering.
 
+e.g.
+
+```bash
+$ docsify start docs
+```
+```
+[SSR] Serving docs now.
+Listening at http://localhost:4000
+```
+
+Serves at [localhost:3000/](http://localhost:3000/)
+
 This runs a Node.js server which pre-renders then serves HTML to the browser. This should make almost no difference to the end-user.
 
 This approach is ideal for scoring higher on search engines, as the pre-rendered HTML is easy for a crawler to read and it does not use up the "crawl budget".
