Correct language about why we do acquisitions on our Ops direction page
Why is this change being made?
Correcting the language on the acquisition plan paragraph:
- Acquisitions help us with both depth and breadth
- We don't want to over-emphasize the role of acquisitions as a tool of help us achieve our roadmap. They are an important tool but we aren't relying on acquisitions as a means to achieve roadmap progress, ie: we don't decide we want to achieve progress in category 'A' only through acquisitions.
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 Eliran Mesika