Fix Transverse Mercator documentation typo

[willschlitzer]

Fixes the Transverse Mercator syntax issues in #2059.

Addresses #2059

Reminders

• Run make format and make check to make sure the code follows the style guide.
• Add tests for new features or tests that would have caught the bug that you're fixing.
• Add new public functions/methods/classes to doc/api/index.rst.
• Write detailed docstrings for all functions/methods.
• If wrapping a new module, open a 'Wrap new GMT module' issue and submit reasonably-sized PRs.
• If adding new functionality, add an example to docstrings or tutorials.
• Use underscores (not hyphens) in names of Python files and directories.

Slash Commands

You can write slash commands (/command) in the first line of a comment to perform
specific operations. Supported slash commands are:

• /format: automatically format and lint the code
• /test-gmt-dev: run full tests on the latest GMT development version

[yvonnefroehlich]

Hm. Do we plan to have separate PRs for each projection? The PR title was renamed to address only the "Transverse Mercator projection". However, there are some more typos to fix, at least the ones listed at #2059 (comment) 🙂.

[willschlitzer]

Hm. Do we plan to have separate PRs for each projection? The PR title was renamed to address only the "Transverse Mercator projection". However, there are some more typos to fix, at least the ones listed at #2059 (comment) slightly_smiling_face.

@yvonnefroehlich I had originally planned to fix all of the typos, but I misinterpreted your original comment as asking for someone to fix them. Since I think there needs to be a bit more explanation on what PyGMT typos need fixing (discussed here) vs. what are issues with GMT documentation, it might just be easier if you submitted a PR with your desired fixes. Happy to help, but I don't want to duplicate effort.

[yvonnefroehlich]

Hm. Do we plan to have separate PRs for each projection? The PR title was renamed to address only the "Transverse Mercator projection". However, there are some more typos to fix, at least the ones listed at #2059 (comment) slightly_smiling_face.

@yvonnefroehlich I had originally planned to fix all of the typos, but I misinterpreted your original comment as asking for someone to fix them. Since I think there needs to be a bit more explanation on what PyGMT typos need fixing (discussed here) vs. what are issues with GMT documentation, it might just be easier if you submitted a PR with your desired fixes. Happy to help, but I don't want to duplicate effort.

No worries @willschlitzer! Firstly, I wanted only to know how to proceed with good first issue issues regarding the release 😉. But it was totally fine that you directly started working on this 🙂.

@GenericMappingTools/pygmt-maintainers and @willschlitzer Should we leave this PR as is and merge it and open a follow up PR for the remaining typo fixes, or do you prefer closing this PR without merging it and opening a new PR including this one typo fix, to have all these typo fixes together in one PR?
I can try working on this on the weekend, but I can not grant for this yet. Maybe we can bump the upstream GMT PR back to after the PyGMT v0.8.0 release?

[seisman]

Should we leave this PR as is and merge it and open a follow up PR for the remaining typo fixes, or do you prefer closing this PR without merging it and opening a new PR including this one typo fix, to have all these typo fixes together in one PR?

Either works. Or you can push more commits directly to this PR.

[yvonnefroehlich]

Should we leave this PR as is and merge it and open a follow up PR for the remaining typo fixes, or do you prefer closing this PR without merging it and opening a new PR including this one typo fix, to have all these typo fixes together in one PR?

Either works. Or you can push more commits directly to this PR.

I prefere working in an own PR on this and starte doing so in PR #2269.

[seisman]

Should we leave this PR as is and merge it and open a follow up PR for the remaining typo fixes, or do you prefer closing this PR without merging it and opening a new PR including this one typo fix, to have all these typo fixes together in one PR?

Either works. Or you can push more commits directly to this PR.

I prefere working in an own PR on this and starte doing so in PR #2269.

OK. I think we can close this PR.