Update the SCORM documentation. Add in extra image for selection step.

[graemeglass]

Add a description of your changes with links to any relevant material.

Date Needed (optional)

If the release date of a feature is known or estimated, provide it to give reviewers guidance on turnaround time.

Reviewers

Possible roles follow. The PR submitter checks the boxes after each reviewer finishes and gives :+1:.

• [ ] Subject matter expert:
• [x] Subject matter expert:
• [x] Product review:
• [ ] Partner support:
• [ ] PM review:

FYI: Tag anyone else who might be interested in this PR here.

Testing

• [x] Ran ./run_tests.sh without warnings or errors

HTML Version (optional)

• [ ] Build an RTD draft for your branch and add a link here

Sandbox (optional)

• [ ] Point to or build a sandbox for the software change and add a link here

Post-review

• [ ] Add a comment with the description of this change or link this PR to the next release notes task.
• [ ] Squash commits

[openedx-webhooks]

Thanks for the pull request, @graemeglass! Please note that it may take us up to several weeks or months to complete a review and merge your PR.

Feel free to add as much of the following information to the ticket as you can:

• supporting documentation
• Open edX discussion forum threads
• timeline information ("this must be merged by XX date", and why that is)
• partner information ("this is a course on edx.org")
• any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.

Please let us know once your PR is ready for our review and all tests are green.

[openedx-webhooks]

@graemeglass 🎉 Your pull request was merged! Please take a moment to answer a two question survey so we can improve your experience in the future.