fixing see also links for txt files

[jesgreco]

fixing see also links for add_video.txt

[openedx-webhooks]

Thanks for the pull request, @jesgreco!

This repository is currently maintained by @openedx/docs-openedx-org-maintainers.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

---

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[jswope00]

I don't think these see also's are thorough enough. Best approach would be to find the navigation section that talks about these tasks, and grab the refs from that.

E.g. for add_html, that is most similar to "Add Text Components" from navigation. Grab those links

[jesgreco]

Changes to the see also tables were made based on navigation files.

[jesgreco]

@jswope00 I think after all my changes this PR is ready for Sarina's review and merge.

[jswope00]

@jesgreco you'll need to eliminate the space in the :ref: links to prevent this kind of error:

[jesgreco]

I'm performing the changes now @jswope00

[jesgreco]

Every file is amended, and tested (build test).

[sarina]

@jswope00 please merge when you're satisfied

[jswope00]

@jesgreco There are some new conflicts. I think because a commit from Sarina touched most of the See Also links. When you fix them, I think you can probably just take your changes over Sarina's in almost every case since Sarina was just fixing spacing whereas you were building out the right links and fixing spacing.

[mphilbrick211]

Hi @jesgreco! Just following up to see if this is still in progress?

[jswope00]

@mphilbrick211 @sarina I recommend closing this PR unmerged since it has been replaced at this point by
#840

In 840, we eliminate the txt files in favor of using snippets of our how-to RST files. So the txt files in this PR end up getting deleted anyway.