Clean up a few more doc sections and links

[GregoryComer]

Summary

Clean up a few remaining placeholders, orphaned pages, and broken links.

Test plan

Built docs locally to verify changes.

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/8672

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

❌ 2 New Failures

As of commit 7ee7942 with merge base 366d87e ():

NEW FAILURES - The following jobs have failed:

• Lint / lintrunner / linux-job (gh)
  >>> Lint for docs/source/backends-xnnpack.md:
• pull / test-llava-runner-linux / linux-job (gh)
  test_generated_output

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[mergennachin]

In this section, (maybe as a follow-up), please remember to add an example CMake file and c++ example runner code that uses XNNPACK (our current xnnpack_runner is too tied our repo, so not that one)

On top of that, we can also add to pytorch-labs/executorch-examples to showcase how it is used from out-of-tree repo.

[mergennachin]

Are the links fixed in https://github.com/pytorch/executorch/tree/executorch-just-works/examples/xnnpack?

I think bunch of links that has "stable/..." will stop working on the next release

I think it makes sense to move from hard-coded "stable/..." prefix to relative path, at least for the links you changed and modify the link name accordingly. There are a few

https://github.com/search?q=repo%3Apytorch%2Fexecutorch%20stable%2F&type=code

[GregoryComer]

Are the links fixed in https://github.com/pytorch/executorch/tree/executorch-just-works/examples/xnnpack?

I think bunch of links that has "stable/..." will stop working on the next release

I think it makes sense to move from hard-coded "stable/..." prefix to relative path, at least for the links you changed and modify the link name accordingly. There are a few

https://github.com/search?q=repo%3Apytorch%2Fexecutorch%20stable%2F&type=code

Good point on the stable docs. Those don't show up as warnings in the doc build, which I've been relying on to catch broken links. I'll see if I can replace all of the stable links with relative links.