Dense paragraph about Premium Plan instances
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 85/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Domain
- documentation
Research direction
Open the Premium Plan instance section at the linked guide and review the quoted paragraph in context. Split the dense sentence into clearer sentences while preserving the usage-limit, workload, and queueing behavior described. Done means the passage is easier to read and translate without changing its meaning.
Written by the indexing model from the issue text.
Description
URL to the relevant guide or resource
https://quantum.cloud.ibm.com/docs/en/guides/instances#premium-plan-instance
Select all that apply
- new content request
- typo
- code bug
- out-of-date content
- broken link
- other
Describe the fix or the content request.
The second sentence is particularly dense due to all the parentheticals:
An administrator can set a usage limit on a Premium Plan instance that applies for the plan's 28-day rolling usage window. If an instance has been marked as "limited" by your administrator (you will see a "Remaining" column in the usage area) and the instance exceeds its allocation (defined by your administrator), any active workload will continue running (including sessions) but pending workloads will remain in the queue until more time is available. If an instance is not limited and the instance exceeds its allocation, jobs run with that instance are likely to run at a lower priority and experience longer queue times.
This makes it hard to read, and probably results in a bad translation. Can the sentence be split up?
For new content requests - if the request is accepted, do you want to write the content?
(No answer)
- Dominant language
- Jupyter Notebook
- Stars
- 106
- Forks
- 223
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 75
Contributor guide
No contributing guide indexed for this repository
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 📄 needs triage 🤔
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Qiskit/documentation#5673 ·
-
content 📄 needs triage 🤔
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Qiskit/documentation#5662 ·
-
content 📄
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Qiskit/documentation#5397 ·
-
ZneOptions typos OpenAPI docs needs triage 🤔
Difficulty 1/5 Under an hour Newbie friendliness 70/100
Qiskit/documentation#5059 · 3 comments ·
-
infra 🏗️ needs triage 🤔
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Qiskit/documentation#5024 ·
All issues in Qiskit/documentation
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Ecosystem: ClawMetry — the Qwen Code reader is now free and open source (follow-up to #9294 / #9338) Opencategory/integration priority/P3 scope/documentation status/ready-for-human type/feature-request
Difficulty 1/5 Under an hour Newbie friendliness 84/100