Clarify open source vs paid features promise on Stewardship page

Amy Brandenburgrequested to merge
abrandenburg-master-patch-17715 into master

Why is this change being made?

We are clarifying on our Stewardship page that when something is open source, we promise we won't take it back, but for paid features, we have the freedom to remove or move certain features to different tiers.

Author Checklist

  • Provided a concise title for the MR
  • Added a description to this MR explaining the reasons for the proposed change, per [say-why-not-just-what][transparency]
  • Assign this change to the correct DRI
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to your manager.
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in [#mr-buddies][mr-buddies-slack].
    • If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files.
Edited by Amy Brandenburg

Merge request reports