Remove cache folder in predeploy script, and refine Markdown formatting

[coder054]

No description provided.

[dsyadav50]

some changes

[sanketBarapatre]

what are these changes?

[lukem512]

The remove cache steps are nice and they helped to resolve a build issue where I bailed out (Ctrl + c) halfway through. It seems odd to bundle that with README updates, however.

[gitname]

Hello @coder054, thank you for submitting a pull request. I am not familiar with that node_modules/gh-pages/.cache folder and have not noticed a need to interact with it directly (e.g. deleting its contents or performing any other action on it).

I want to avoid having unnecessary steps in the process. To that end, I want to better understand the step you are proposing (i.e. the step of deleting the aforementioned folder). In what situation does that step provide a benefit? How can I get a repo into a state in which I can witness the effect of the step (i.e. so I can manually test the step)?

@lukem512 suggested killing the build process part way through would put a repo into such a state.

The remove cache steps are nice and they helped to resolve a build issue where I bailed out (Ctrl + c) halfway through...

Maybe that's the same situation you had in mind.

On a side note, I also agree with @lukem512's feedback that:

It seems odd to bundle that with README updates

I know sometimes code editors automatically reformat entire files as soon as the file has been saved. I suspect that is what happened here.