Minor grammatical updates; linking to Apache 2.0 official license page; changing reference from "project owners" to advisors.

Author: jstrauss

README.md

@@ -7,30 +7,30 @@ Welcome to the Progress Chef Open Source community!
 This is your home for contributing to Progress Chef’s ecosystem. Whether you're improving a Chef Infra resource, improving documentation, crafting an InSpec control, extending Cookstyle, or building a new plugin — you’re in the right place.
 
 ## How We're Organized
-Progress Chef (the company) produces a range of infrastructure automation products such as **Chef Infra**, **Chef InSpec**, **Chef Habitat**, and the supporting ecosystem. These products are released and managed under Progress Chef’s **[Open Core](./policies/open-core.md)** model. 
+Progress Software (the company) produces a range of Chef infrastructure automation products, such as **Chef Infra**, **Chef InSpec**, **Chef Habitat**, and the supporting ecosystem. These products are released and managed under Progress Chef’s **[Open Core](./policies/open-core.md)** model. 
 
-All Progress Chef Open Source projects are released and under the Apache 2.0 license. These open source projects serve as the shared foundation for our global community; while advanced features and platform capabilities are part of the Chef 360 commercial offerings.
+All Progress Chef Open Source projects are released and under the [Apache 2.0 license](https://www.apache.org/licenses/LICENSE-2.0). These open source projects serve as the shared foundation for our global community, while advanced features and platform capabilities are part of the Chef 360 commercial offerings.
 
 Many of the Progress Chef products includes one or more open source [projects](./projects/README.md) — for example, the Chef Infra product is comprised of `chef`, `ohai`, various `mixlib` libraries, and other interdependent tools. 
 
-All open source projects operate and governed by the policies outlined in our [Governance](./policies/governance.md) document.
+All open source projects operate under and are governed by the policies outlined in our [Governance](./policies/governance.md) document.
 
-We decide on long-term plans and direction through structured [Project Planning](./contributors/guide/project-planning.md) and [Triage and Prioritization](./contributors/guide/README.md#issues-management-or-triage) processes.
+We decide on long-term plans and direction through structured [Project Planning](./contributors/guide/project-planning.md) and our [Triage and Prioritization](./contributors/guide/README.md#issues-management-or-triage) processes.
 
 ## Join Us in Building the Future
-Whether you're a long-time contributor or a first-time user, we invite you to help shape the future of infrastructure automation. We are only as strong as the community around it — and we’re committed to making Chef an ecosystem worth building together.
+Whether you're a long-time contributor or a first-time user, we invite you to help shape the future of infrastructure automation. We are only as strong as the community around it — and we’re committed to making Chef's ecosystem one that is worth building together.
 
 ### Getting Started Contributing
 1. Browse the [Projects List](./projects/README.md) to find something you care about.
 2. Read the relevant CONTRIBUTING guide for that project (see project for details).
-4. How to [find something to work on](./contributors/guide/README.md#find-something-to-work-on)
-5. How to [open a pull request](./contributors/guide/README.md#open-a-pull-request)
+3. Learn how to [find something to work on](./contributors/guide/README.md#find-something-to-work-on).
+4. Learn how to [open a pull request](./contributors/guide/README.md#open-a-pull-request).
 
 Visit the [Contributor Guide](./contributors/guide/README.md) for help filing issues, opening PRs, and more.
 
 ## Project Membership
 
-We encourage all contributors to become project members. We aim to grow an active, healthy community of contributors, reviewers, and project owners. Learn about requirements and perks of membership in our [Project Membership](./policies/project-membership.md) page.
+We encourage all contributors to become project members. We aim to grow an active, healthy community of contributors, reviewers, and advisors. Learn about the requirements and perks of membership on our [Project Membership](./policies/project-membership.md) page.
 
 ## Communicating With Us