[doc]Fix autograd.detect_anomaly docs incorrectly formatted

[lacrosse91]

Fixes #51141

Two bullet points don't render as bullet points.

Before

After

[facebook-github-bot]

Hi @lacrosse91!

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@fb.com. Thanks!

[facebook-github-bot]

💊 CI failures summary and remediations

As of commit 38154d3 (more details on the Dr. CI page):

---

• 1/9 failures possibly* introduced in this PR
  • 1/1 non-CircleCI failure(s)
• 8/9 broken upstream at merge base 534aabc since Jan 28

---

🚧 5 ongoing upstream failures:

These were probably caused by upstream breakages that are not fixed yet.

• pytorch_linux_xenial_cuda10_2_cudnn7_py3_gcc7_test1 since Jan 28 (05c8cd7)
  • 🔁 rerun
• pytorch_linux_xenial_py3_6_gcc5_4_test since Jan 28 (916af89)
  • 🔁 rerun
• pytorch_linux_xenial_py3_clang5_asan_test2 since Jan 28 (05c8cd7)
  • 🔁 rerun
• pytorch_linux_xenial_cuda10_2_cudnn7_py3_gcc7_test2 since Jan 28 (916af89)
  • 🔁 rerun
• pytorch_linux_bionic_py3_6_clang9_test since Jan 28 (05c8cd7)
  • 🔁 rerun

🚧 3 fixed upstream failures:

These were probably caused by upstream breakages that were already fixed.

Please rebase on the viable/strict branch (expand for instructions)

If your commit is older than viable/strict, run these commands:

git fetch https://github.com/pytorch/pytorch viable/strict
git rebase FETCH_HEAD

Check out the recency history of this "viable master" tracking branch.

• pytorch_linux_xenial_py3_clang5_asan_test1 from Jan 28 until Jan 29 (05c8cd7 - 5a406c0)
  • 🔁 rerun
• pytorch_windows_vs2019_py36_cuda10.1_test1 from Jan 28 until Jan 29 (05c8cd7 - c096691)
  • 🔁 rerun
• pytorch_windows_vs2019_py36_cuda10.1_test2 from Jan 28 until Jan 29 (05c8cd7 - c096691)
  • 🔁 rerun

---

This comment was automatically generated by Dr. CI (expand for details).

Follow this link to opt-out of these comments for your Pull Requests.

Please report bugs/suggestions to the (internal) Dr. CI Users group.

[facebook-github-bot]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

[facebook-github-bot]

@ezyang has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

[facebook-github-bot]

@ezyang merged this pull request in c41ca4a.