Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fixed typo #2512

Closed
wants to merge 1 commit into from
Closed

fixed typo #2512

wants to merge 1 commit into from

Conversation

ne7ermor3
Copy link

cleaned up some instances of typo throughout the documentation, namely "each each" instead of "each".

@qiskit-bot
Copy link
Contributor

Thanks for contributing to Qiskit documentation!

Before your PR can be merged, it will first need to pass continuous integration tests and be reviewed. Sometimes the review process can be slow, so please be patient. Thanks! 🙌

@CLAassistant
Copy link

CLAassistant commented Dec 20, 2024

CLA assistant check
All committers have signed the CLA.

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@Eric-Arellano
Copy link
Collaborator

Eric-Arellano commented Dec 20, 2024

Hey @ne7ermor3 , thank you! Pardon we didn't make this more clear. To fix Qiskit/qiskit#13576, you'll need to open PRs in https://github.com/Qiskit/qiskit and https://github.com/Qiskit/qiskit-ibm-runtime to fix the Python docstring. That's because the API docs are generated from Sphinx in those two repositories and converted into the MDX files you see here. So, your current PR would be reverted the next time we re-generate the API docs.

If you're willing, we'd love a PR in those two repositories!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

4 participants