Update stale recipes/quickstart paths to getting-started

[PedroooAlmeida]

What does this PR do?

The repo refactor renamed recipes/quickstart → getting-started (documented in UPDATES.md), but several docs still reference the old path in torchrun/sbatch commands and link text. Users following these instructions verbatim hit a "file not found" error since recipes/quickstart/finetuning/finetuning.py no longer exists at that path.

This PR updates 5 docs to point to the current location at getting-started/finetuning/. It also fixes a pre-existing typo where finetune_vision_model.md referenced a singular dataset folder; the actual folder is datasets (plural). The RAFT-Chatbot README also had a separate stale path (recipes/finetuning/datasets/raft_dataset.py) which was updated in the same fix.

Files changed:

• getting-started/finetuning/finetune_vision_model.md (3 torchrun examples + 1 typo fix)
• getting-started/finetuning/multigpu_finetuning.md (sbatch path)
• getting-started/finetuning/datasets/README.md (link text)
• getting-started/inference/local_inference/README.md (torchrun example)
• end-to-end-use-cases/RAFT-Chatbot/README.md (two stale paths in one torchrun example)

Feature/Issue validation/testing

Verified by inspecting the repo at current main:

• getting-started/finetuning/finetuning.py exists at the new path
• getting-started/finetuning/multi_node.slurm exists at the new path
• getting-started/finetuning/datasets/ is the actual folder name (plural)
• getting-started/finetuning/datasets/raft_dataset.py exists at the new path
• recipes/quickstart/finetuning/ no longer exists in the repo
• git grep "recipes/quickstart/finetuning" after the change returns no results in user-facing docs (only UPDATES.md, which legitimately documents the rename)

Before submitting

• 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, Pull Request section?
• Was this discussed/approved via a Github issue? Please add a link to it if that's the case.
• Did you make sure to update the documentation with your changes?
• Did you write any new necessary tests? (N/A — docs-only change)

[meta-cla]

Hi @PedroooAlmeida!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

[meta-cla]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!