fix: typos
Author: testwill
Pull request: yes

# What does this PR do?

<!--
Congratulations! You've made it this far! You're not quite done yet though.

Once merged, your PR is going to appear in the release notes with the title you set, so make sure it's a great title that fully reflects the extent of your awesome contribution.

Then, please replace this with a description of the change and which issue is fixed (if applicable). Please also include relevant motivation and context. List any dependencies (if any) that are required for this change.

Once you're done, someone will review your PR shortly (see the section "Who can review?" below to tag some potential reviewers). They may suggest changes to make the code even better. If no one reviewed your PR after a week has passed, don't hesitate to post a new comment @-mentioning the same persons---sometimes notifications get lost.
-->

<!-- Remove if not applicable -->

Fixes # (issue)


## Before submitting
- [x] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
- [ ] Did you read the [contributor guideline](https://github.com/huggingface/transformers/blob/main/CONTRIBUTING.md#create-a-pull-request),
      Pull Request section?
- [ ] Was this discussed/approved via a Github issue or the [forum](https://discuss.huggingface.co/)? Please add a link
      to it if that's the case.
- [ ] Did you make sure to update the documentation with your changes? Here are the
      [documentation guidelines](https://github.com/huggingface/transformers/tree/main/docs), and
      [here are tips on formatting docstrings](https://github.com/huggingface/transformers/tree/main/docs#writing-source-documentation).
- [ ] Did you write any new necessary tests?


## Who can review?

Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.

<!-- Your PR will be replied to more quickly if you can figure out the right person to tag with @

 If you know how to use git blame, that is the easiest way, otherwise, here is a rough guide of **who to tag**.
 Please tag fewer than 3 people.

Models:

- text models: @ArthurZucker and @younesbelkada
- vision models: @amyeroberts
- speech models: @sanchit-gandhi
- graph models: @clefourrier

Library:

- flax: @sanchit-gandhi
- generate: @gante
- pipelines: @Narsil
- tensorflow: @gante and @Rocketknight1
- tokenizers: @ArthurZucker
- trainer: @muellerzr and @pacman100

Integrations:

- deepspeed: HF Trainer/Accelerate: @pacman100
- ray/raytune: @richardliaw, @amogkam
- Big Model Inference: @SunMarc
- quantization (bitsandbytes, autogpt): @SunMarc and @younesbelkada

Documentation: @stevhliu and @MKhalusova

HF projects:

- accelerate: [different repo](https://github.com/huggingface/accelerate)
- datasets: [different repo](https://github.com/huggingface/datasets)
- diffusers: [different repo](https://github.com/huggingface/diffusers)
- rust tokenizers: [different repo](https://github.com/huggingface/tokenizers)

Maintained examples (not research project or legacy):

- Flax: @sanchit-gandhi
- PyTorch: See Models above and tag the person corresponding to the modality of the example.
- TensorFlow: @Rocketknight1

 -->


Comments:
@testwill There's a failing CI test which will need to pas before merging in. Running `make fix-copies` and pushing the changes should resolve this. 

python utils/check_copies.py --fix_and_overwrite
  File "utils/check_copies.py", line 177
    def _is_definition_header_ending_line(line: str) -> bool:
                                              ^
SyntaxError: invalid syntax
make: *** [Makefile:82: fix-copies] Error 1


hmmm, that's odd. I'm able to run `make fix-copies` locally and just from the error the syntax looks OK. If you run `python` in your environment, which version is it running? You can check this by doing `python -V`

Python 2.7.18

The docs for this PR live [here](https://moon-ci-docs.huggingface.co/docs/transformers/pr_29653). All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

OK, that's the issue, the library only supports python3. 

The recommended way to develop is to work from a python3 virtual environment, in which `python` will run python 3.x. Transformers requires python>= 3.8. 

Python 3.8.10 ,Also installed in the local environment

@testwill I'm assuming that you run python 3.8 through the `python3` command? All of the scripts in the library use `python`, and so by running [`make fix-copies` outside of a virtual environment, you'll be running python 2.7.18](https://github.com/huggingface/transformers/blob/f738ab3b5d30e30c43a4c3d00ca8939f8a4d4427/Makefile#L81), which results in this error 

run cmd
echo "alias python=python3" >> ~/.bashrc
source ~/.bashrc

same error

@testwill I don't suggest setting an alias like this, as it can lead to all sorts of weird behaviour. As per the contribution guidelines, I suggest making a virtual env and running from there.


        modified:   README_de.md
        modified:   README_pt-br.md
        modified:   README_ru.md
        modified:   README_te.md
        modified:   README_vi.md
        modified:   src/transformers/models/beit/image_processing_beit.py
        modified:   src/transformers/models/bigbird_pegasus/modeling_bigbird_pegasus.py
        modified:   src/transformers/models/blip/image_processing_blip.py
        modified:   src/transformers/models/bridgetower/image_processing_bridgetower.py
        modified:   src/transformers/models/chinese_clip/image_processing_chinese_clip.py
        modified:   src/transformers/models/clip/image_processing_clip.py
        modified:   src/transformers/models/convnext/image_processing_convnext.py
        modified:   src/transformers/models/donut/image_processing_donut.py
        modified:   src/transformers/models/dpt/image_processing_dpt.py
        modified:   tests/models/roc_bert/test_tokenization_roc_bert.py
Do all these documents need to be committed?

@testwill No, you shouldn't need to add these. Can you rebase on main to include any recent upstream changes? This should fix this 

ok