The assembly introduction lists the capabilities: "After installing {builds-shortname}, you can create builds... You can also delete custom resources...". This clearly states what the user will learn to do, but it could be improved by explicitly stating the high-level benefit or impact (e.g., "This documentation enables you to customize and manage your application deployment pipelines...").

Highlight sections where this aspect could be improved: The assembly abstract provides a clear "what" (creating various builds and deleting resources) but lacks an explicit "why" or statement of the overall user benefit/impact.