Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

Automatically generated comment ℹ️

This comment is automatically generated and will be overwritten every time changes are committed to this branch.

The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data directory will not show up in this table.

Content directory changes

You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.

fpt: Free, Pro, Team
ghec: GitHub Enterprise Cloud
ghes: GitHub Enterprise Server
ghae: GitHub AE

Ah, ok. So only AFTER submitting the PR do we see the "view deployment" option. That's a bit confusing (to have to agree to having done it before it's possible.)

Anyway, I see now that there IS one problem--in that I had used the "autotitle" feature but it's not working for one of the two links I added. And I won't be able to edit this file whose commit I've offered (at least in the Github web UI for proposing doc changes, it doesn't seem possible.)

But lest someone close this due to that failure, I'll point out that the title for the page in question is, "Customer Terms", so if a maintainer seeing this wanted to slip in that change after/while accepting mine, that would resolve things.

Clearly, I'm not a pro-level github user--and I'm only using this web UI vs rebuilding the docs locally. I hope you can tell I'm simply trying to help improve the docs, as I am in fact reading them to better understand things. :-)

@carehart Thanks so much for opening a PR, and the thorough explanation on your thoughts process 💛 I'll get this triaged for review ✨

@carehart Thank you for raising a PR! I agree with the change you recommend here, in terms of customer experience.

A few things to note. I'll reply in-line to your comments:

Ah, ok. So only AFTER submitting the PR do we see the "view deployment" option. That's a bit confusing (to have to agree to having done it before it's possible.)

Apologies this wasn't clear—you might find this page useful https://docs.github.com/en/contributing/collaborating-on-github-docs/about-contributing-to-github-docs#reviewing-your-own-pull-requests. I'll discuss internally whether there's anything more we can do to make that experience better for users here. Another option (in future) would be to run the documentation locally, so that you can see changes you make in a local preview instance, without needing to submit a PR first.

Anyway, I see now that there IS one problem--in that I had used the "autotitle" feature but it's not working for one of the two links I added.

You were quite right to use AUTOTITLE; the only problem was that that feature only works with docs.github.com pages, and the page in question is a github.com page. Hence my "suggestion" (see below comment for context).

And I won't be able to edit this file whose commit I've offered (at least in the Github web UI for proposing doc changes, it doesn't seem possible.)

I've made a "suggestion" that you can apply. I agree the Web UI is a little limited in this respect in terms of making further changes to an already submitted PR. For future reference: you should also have been able to make a "suggestion" yourself, even if that's a little bit awkward, so I've included the docs page describing that feature in an in-line link at the start of this paragraph for your reference.

In any case, once we've resolved the outstanding point, I'll be happy to get this merged 😄