Correcting run-on sentences in API-doc

[Shivansh20128]

Description

This PR corrects the run-on sentences in the API Docs inside the kwargs and scale factors. It #Resolves #2422.
I have some blank lines before the bullet points and corrected indentations. The doc build looks good now.

This is how it looked earlier.

And this is how it looks now:

---

License

• I license this contribution under the terms of the GNU GPL, version 3 and grant Unitary Fund the right to provide additional permissions as described in section 7 of the GNU GPL, version 3.

Before opening the PR, please ensure you have completed the following where appropriate.

• I added unit tests for new code.
• I used type hints in function signatures.
• I used Google-style docstrings for functions.
• I updated the documentation where relevant.
• Added myself / the copyright holder to the AUTHORS file

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.73%. Comparing base (7648648) to head (1ae2fc7).
Report is 7 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2589   +/-   ##
=======================================
  Coverage   98.73%   98.73%           
=======================================
  Files          92       92           
  Lines        4174     4183    +9     
=======================================
+ Hits         4121     4130    +9     
  Misses         53       53           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[cosenal]

@Shivansh20128 notice that the docs-build is failing with this change. You can test it locally with make docs

[Shivansh20128]

I have added the spaces and blank lines wherever required. The docs should look fine now. Let me know if anything else is required here.
Thanks

[natestemen]

Thanks for the PR! I haven't had a thorough look yet, but two things.

1. Can you add a PR description, including a link to the issue this is related to?
2. The documentation build is still failing. If you've already tried to resolve this issue, please document what you found in the PR description as context for a reviewer, or otherwise give it a shot! Feel free to ask questions on the Discord in the Mitiq channel too!

Once these are done, please mark the PR as ready for review and we'll take a detailed look.

[purva-thakre]

scale_noise is repeated twice here.

[purva-thakre]

@Shivansh20128 Feel free to ignore all the resolved suggestions made by me. I think what I am suggesting could be tackled in another issue.