[Docs] Remove duplicated comments
Author: lorenzoverardo
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 https://github.com/huggingface/transformers/issues/29814


## 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

 -->

Must be a result of [this script](https://github.com/huggingface/transformers/blob/v3.5.1hotfix/utils/style_doc.py) by @sgugger, who, however, I noticed that doesn't work at the company anymore.
cc @stevhliu @MKhalusova

Comments:
No worries! These files don't seem to exist on `main` as it's legacy docs, and I opened this PR against `v3.5.1hotfix` as I thought that's what the source is for https://huggingface.co/transformers/v3.5.1/index.html, but I actually just noticed that the problem still exists on later versions (>4.0.0). Do you still think I should change the target to `main`?

Ah I see! On my end, I don't see these duplicated comments any more on the latest versions of Transformers. For example, this is from v4.39.1:

<img width="830" alt="Screenshot 2024-03-23 at 12 00 11 PM" src="https://github.com/huggingface/transformers/assets/59462357/5633669f-4b83-45cd-bfc2-d4b148d7075f">

And it looks ok from here: https://github.com/huggingface/transformers/blob/dafe37025547597164e6d2efbfaff06f2404237c/src/transformers/models/auto/auto_factory.py#L41

As far as I can tell, there are a variable number of duplicates of this kind for all versions going from v3.2.0 all the way to v4.4.2. Do you not update these seemingly legacy docs anymore or do you have some kind of backporting process I can follow perhaps?

That's a good question, and I'm not actually sure! Let me ping @ArthurZucker who can better help answer this :)

We don't really have anything TBH, and yeah we should delete if possible ! 

@stevhliu what do you advise? Should these docs be updated or not? If so, how would I go about it, considering that tests are not passing for this version (due to dependency hell, it seems), and also all versions affected would ideally need to be fixed (I'm also not sure about the respective branch of each)? 

I would say we don't really need to update and maintain these legacy docs anymore, and users are redirected to the newer doc versions where it is fixed and correct.

Okay then, I'll close the PR 🙂