The way to launch Sugarizer locally with Chrome has changed

[ricknjacky]

A recent discussion on sugarlabs mailing list has rightly brought this to our attention that the path{as mentioned in markdown files} via which we open sugarizer in our browser is actually incorrect.

Even I faced this issue where, upon running the following command:

chrome --allow-file-access-from-files index.html

A blank page opens up,

to tackle this I always opened the index.html file navigating into the directory where it resides. This is however a heuristic approach and I presume not the right way to access sugarizer in browser locally.

[llaske]

Fixed in #938