Fix for #7149 + proposed readme for docker on Windows + fixing typos

[joseph-sch]

Type

• Bug fix (non-breaking change which fixes an issue): Fixes Typo in argument of o3d.geometry.TriangleMesh.create_mobius and in o3d.t.geometry.TriangleMesh.create_mobius #7149
• New feature (non-breaking change which adds functionality). Resolves #
• Breaking change (fix or feature that would cause existing functionality to not work as expected) Resolves Typo in argument of o3d.geometry.TriangleMesh.create_mobius and in o3d.t.geometry.TriangleMesh.create_mobius #7149

Motivation and Context

1. There is a typo in o3d.geometry.TriangleMesh.create_mobius and in o3d.t.geometry.TriangleMesh.create_mobius: raidus instead of radius as explained in Typo in argument of o3d.geometry.TriangleMesh.create_mobius and in o3d.t.geometry.TriangleMesh.create_mobius #7149
2. Some typos throughout the docstrings, comments and a string
3. Proposing a markdown readme for docker on Windows - or should it be part of the docker.in.rst file in order to appear within https://www.open3d.org/docs/latest/docker.html#building-open3d-in-docker?

Checklist:

• I have run python util/check_style.py --apply to apply Open3D code style
  to my code.
• This PR changes Open3D behavior or adds new functionality.
  • Both C++ (Doxygen) and Python (Sphinx / Google style) documentation is
    updated accordingly.
  • I have added or updated C++ and / or Python unit tests OR included test
    results (e.g. screenshots or numbers) here.
• I will follow up and update the code if CI fails.
• For fork PRs, I have selected Allow edits from maintainers.

Description

[update-docs]

Thanks for submitting this pull request! The maintainers of this repository would appreciate if you could update the CHANGELOG.md based on your changes.

[timohl]

All good small fixes.

I would mark this PR as breaking change though, since a parameter name changed (with good reason).
It is just a typo fix, but existing calls using named parameters would break.

I cannot say much to the content of the docker windows readme, but there is also docker/README.md where this could be included as a section (or in docs/docker.in.rst as you mentioned.
Not sure if it is a good idea to have 3 different spots documenting docker builds.

[joseph-sch]

All good small fixes.

I would mark this PR as breaking change though, since a parameter name changed (with good reason). It is just a typo fix, but existing calls using named parameters would break.

I cannot say much to the content of the docker windows readme, but there is also docker/README.md where this could be included as a section (or in docs/docker.in.rst as you mentioned. Not sure if it is a good idea to have 3 different spots documenting docker builds.

Thank you for the feedback

1. indeed technically it's a breaking change, I've updated the description
2. I can split the instructions that I proposed between a short mention in docs/docker.in.rst and detailed instructions in docker/README.md - would that be OK?

[timohl]

2. I can split the instructions that I proposed between a short mention in docs/docker.in.rst and detailed instructions in docker/README.md - would that be OK?

Something like that sounds good I think, but somebody else should review that, since I am not using open3d+docker.