Consistent capitalization of macOS

[techne98]

This probably seems very nitpicky or minutiae, but there is some inconsistent capitalization across mentions of macOS on the website.

For example:

In the install/#macos section, the Navbar, link, title, and inline references are mostly "MacOS", with one "macOS".

However, on the install/on_mac_os page, the title uses "macOS" and inline references are macOS.

"macOS" seems to be the current preferred capitalization by Apple. In any case, consistent use of macOS (or MacOS) is desired.

I know this probably seems very minor, but in my work I find that small details can add up and improving them can lead to an overall feeling of higher quality of both product and documentation.

I hope my suggestions prove helpful, and appreciate all of the hard work that has gone into Crystal!

[techne98]

Hi @straight-shoota - I saw you gave this a thumbs up, so I started working on a draft PR (#1012).

The only question I have is about the "MacOS" in the install Navbar. I couldn't quite find out where to update it - I played around with _data/nav.yml and _data/install.yaml and removed the cache, but I didn't notice any updates.

I also didn't want to start messing with the style of Navbar links in case the style of it is intentional (everything starts with a capital, e.g. including Asdf instead of asdf), and I'm not super familiar with Ruby/Jekyll.

In the meantime if you get a chance to check out the draft PR and let me know if it looks good and I can mark it as ready for review.

Thanks,

Jack

[straight-shoota]

The install navbar is defined in _data/nav.yml. Changing the spelling there should update it.
If that didn't work, maybe there is still something cached somewhere... 🤷 You might want to delete the build folder and run jekyll build instead of serve (shortcut: make clean build).
Or just add the change to the PR and it'll build in netlify.

[techne98]

Appreciate the notes! I'll have a play with the local build folder and see what happens there.

In the meantime, I'll push a commit and take a look at the preview deployment.