Typo/text correction in get-started-with-sampler
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 88/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- jupyter-notebook
- Domain
- documentation
Research direction
The sentence to change is the first line of step 1, "Initialize the account", in the Sampler quickstart guide get-started-with-sampler. Find that sentence in the source for the guide in this repository, which is likely a Jupyter notebook or Markdown file, and replace "to calculate the expectation value" with a phrase that matches the Sampler's role, such as "to process one or more quantum circuits". Done means the sentence reads correctly in the source and the guide still builds.
Written by the indexing model from the issue text.
Description
URL to the relevant guide or resource
Go to URL : https://quantum.cloud.ibm.com/docs/en/guides/get-started-with-sampler
In "Sampler quickstart", go to "Steps to use the Sampler primitive"
Now, go to, "1. Initialize the account".
First line is "You first need to initialize your account. You can then select the QPU you want to use to calculate the expectation value."
Select all that apply
- new content request
- typo
- code bug
- out-of-date content
- broken link
- other
Describe the fix or the content request.
Here Sampler primitives are discussed. The Sampler's core task is to sampling the output register from the execution of one or more quantum circuits on selected QPU, returns measurement outcome distributions, bitstrings, or quasi-probability distributions. With respect to Sampler primitives it is not used "to calculate the expectation value". So it is not correct or logical to say "select the QPU you want to use to calculate the expectation value."
Instead of line "You first need to initialize your account. You can then select the QPU you want to use to calculate the expectation value."
We can have one of following option (suggestion only)
-
"You first need to initialize your account. You can then select the QPU you want to use"
-
"You first need to initialize your account. You can then select the QPU you want to use to process one or more quantum circuits"
For new content requests - if the request is accepted, do you want to write the content?
(No answer)
- Dominant language
- Jupyter Notebook
- Stars
- 108
- Forks
- 236
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 70
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Qiskit/documentation
-
content 📄
Difficulty 1/5 1-3 hours Newbie friendliness 68/100
Qiskit/documentation#5808 ·
Maintainers usually reply within 1 day
-
Document resource unit fields in service instance API guidePossibly taken @AryanSilver24 claimed this 5 days ago. Opencontent 📄
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Qiskit/documentation#5790 ·
Maintainers usually reply within 1 day
-
Three defects in `sphinx-alt-text-validator`May be free again @kesavan272006 claimed this 25 days ago, and no pull request is open. Opencontent 📄 infra 🏗️
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Qiskit/documentation#5693 · 1 comment ·
Maintainers usually reply within 1 day
-
Add new images to ParityQC guidePossibly taken @abbycross claimed this 24 days ago. Opencontent 📄
Difficulty 1/5 Under an hour Newbie friendliness 70/100
Qiskit/documentation#5686 · 1 assignee ·
Maintainers usually reply within 1 day
-
content 📄
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Qiskit/documentation#5673 · 2 comments ·
Maintainers usually reply within 1 day
All issues in Qiskit/documentation
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ubuntu/ubuntu-project-docs#850 ·
Maintainers usually reply within 1 day
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
githubnext/gh-aw-workshop#4755 ·
Maintainers usually reply within 1 day
-
fix
Difficulty 1/5 Under an hour Newbie friendliness 72/100
idean3885/claude-ops-agent#728 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 67/100