Minor updates, typos, add vscode auto formatting

[jahow]

• corrected several minor typos
• reworded a few parts
• fixed/added some code extracts
• fixed params for getting ngrok to run
• rewrote the heading part of the mobile app; it wasn't working on my mobile, now it works on chrome only; this might be worth checking some more
• added a .vscode/settings file to enable auto formatting in vscode; I found that when copy pasting the resulting code wouldn't look great without this

Another small thing I've noticed during the workshop: npm install fails on vite with node 14.17

$ npm install
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'vite@3.0.8',
npm WARN EBADENGINE   required: { node: '^14.18.0 || >=16.0.0' },
npm WARN EBADENGINE   current: { node: 'v14.17.0', npm: '7.18.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'vite-plugin-static-copy@0.7.0',
npm WARN EBADENGINE   required: { node: '^14.18.0 || >=16.0.0' },
npm WARN EBADENGINE   current: { node: 'v14.17.0', npm: '7.18.1' }
npm WARN EBADENGINE }

added 241 packages, and audited 242 packages in 6s

66 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

$ npm -v
7.18.1

$ node -v
v14.17.0

I think it would make sense to advertise node 14.18 (or node 16) as a minimum requirement?

[ahocevar]

I think it makes sense to require at least Node 16, and I added a suggestion for the device orientation example.

[jahow]

I'm not adding any node requirement in the package.json for now to avoid unnecessary failures on npm install, maybe after FOSS4G ;) thanks for the review!

[tschaub]

I removed the src/en/.vscode/settings.json file in #153. I agree these are nice settings (and use them as well), but I think it works better if we do not commit OS- or editor-specific configuration files to the repo. Instead, I think it works well if you add your favorite editor's configuration files to your global gitignore file. Then we don't need to commit files for every OS/editor and we don't have to worry about conflicts in editor preferences.

So an example global ~/.gitignore file might look something like this:

.DS_Store
.vscode/

Then I don't need to worry about adding files matching those patterns to every repo, and I don't need to add them to every project's gitignore file.

Hope this doesn't sound pedantic. In this case, I already had a src/en/.vscode/settings.json file with settings that conflicted with the ones you added here (I have slightly different formatting settings at the user level, and I had a workspace setting here that override one of my user settings).

Thanks for the typo fixes and grammar changes.

I was able to get the heading stuff to work on Safari on my phone fwiw (with your changes).