[Task]: Normalize `typehint` vs. `type-hint` vs. `type hint` in Python documentation and docstrings
Open
P3
task
website
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 196
Description
### What needs to happen?
See https://github.com/apache/beam/pull/23909#discussion_r1011974873
We use three different formats to represent "type hint" in Python documentation and docstrings. We should pick one and standardize on it across all documentation on the Beam website and in docstrings.
### Issue Priority
Priority: 3
### Issue Component
Component: website
Contributor guide
Assessment
This issue has not been assessed yet.