Update wording on Resume subscription to Turn on auto-renew

What does this MR do?

Solves customers-gitlab-com#4964 (closed)

After https://gitlab.com/gitlab-org/customers-gitlab-com/-/merge_requests/7299 is merged, this changed the wording in the docs.

Update the wording on this button to make it clearer that it's just toggling the auto-renewal status.

1. Change Resume subscription to Turn on auto-renew.
2. Keep Cancel subscription button as is.

Related issues

customers-gitlab-com#4964 (closed)

Author's checklist

• Optional. Consider taking the GitLab Technical Writing Fundamentals course.
• Follow the:
  • Documentation process.
  • Documentation guidelines.
  • Style Guide.
• If you're adding or changing the main heading of the page (H1), ensure that the product tier badge is added.
• If you are a GitLab team member, request a review based on:
  • The documentation page's metadata.
  • The associated Technical Writer.

If you are a GitLab team member and only adding documentation, do not add any of the following labels:

• ~"frontend"
• ~"backend"
• ~"type::bug"
• ~"database"

These labels cause the MR to be added to code verification QA issues.

Reviewer's checklist

Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.

If you aren't sure which tech writer to ask, use roulette or ask in the #docs Slack channel.

• If the content requires it, ensure the information is reviewed by a subject matter expert.
• Technical writer review items:
  • Ensure docs metadata is present and up-to-date.
  • Ensure the appropriate labels are added to this MR.
  • Ensure a release milestone is set.
  • If relevant to this MR, ensure content topic type principles are in use, including:
    • The headings should be something you'd do a Google search for. Instead of Default behavior, say something like Default behavior when you close an issue.
    • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure GDK.
    • Any task steps should be written as a numbered list.
    • If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
• Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.

added docsimprovement documentation maintenancerefactor typemaintenance labels

assigned to @minahilnichols

	1 Message
	This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge.

Documentation review

The following files require a review from a technical writer:

• doc/subscriptions/gitlab_com/index.md (Link to current live version)
• doc/subscriptions/self_managed/index.md (Link to current live version)

The review does not need to block merging this merge request. See the:

• Metadata for the *.md files that you've changed. The first few lines of each *.md file identify the stage and group most closely associated with your docs change.
• The Technical Writer assigned for that stage and group.
• Documentation workflows for information on when to assign a merge request for review.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

added SMAutoRenew label

added 1 deleted label

added UX devopsfulfillment groupsubscription management maintenanceusability sectionfulfillment severity3 labels and removed maintenancerefactor label

changed milestone to %16.0

added Category:Subscription Management label

added docs-only label

marked this merge request as ready

changed the description

@kpaizee will you run an initial review here? I'm not sure who else should be tagged here, please let me know.

requested review from @kpaizee

approved this merge request

added Technical Writing label

Hi @kpaizee ,

GitLab Bot has added the Technical Writing label because a Technical Writer has approved or merged this MR.

This message was generated automatically. You're welcome to improve it.

resolved all threads

enabled an automatic merge when the pipeline for 362a10a1 succeeds

merged

mentioned in commit ac61c99d

added workflowstaging-canary label

added workflowcanary label and removed workflowstaging-canary label

added workflowstaging label and removed workflowcanary label

added workflowproduction label and removed workflowstaging label

added releasedcandidate label

added workflowpost-deploy-db-staging label and removed workflowproduction label