gdocs, style fixes to projects

Author: MattDodsonEnglish

docs/sources/projects-and-users/manage-project-members.md

@@ -14,18 +14,18 @@ A k6 project member is a Grafana user with access to a particular [k6 project]({
 
 Grafana Cloud k6 uses the following roles to control user access:
 
-- **Admin**: Has access to all the resources. 
-- **Editor**: Can create and run tests.
-- **Viewer**: Can only view tests.
+- **Admin**. Can access to all the resources.
+- **Editor**. Can create and run tests.
+- **Viewer**. Can only view tests.
 
 ## Grant member roles
 
-### Before you begin
+**Before you begin:**
 
-- Ensure that you are an admin of the k6 project
-- The new project member must be a Grafana organization member and have logged into the Grafana Stack of the k6 project
+- Ensure that you are an admin of the k6 project.
+- The new project member must be a Grafana organization member and have logged into the Grafana Stack of the k6 project.
 
-To grant a role to a team member in a k6 project:
+Then, to grant a role to a team member in a k6 project, follow these steps:
 1. Click **Projects** on the k6 sidebar.
 2. Click the **Project Settings** (gear) icon of the particular project.
 3. Click the **Add users** button.

docs/sources/projects-and-users/projects.md

@@ -8,20 +8,22 @@ aliases:
 
 # Projects
 
-Projects allow to organize k6 tests in collections and grant their access. Here are some ways we users use Projects to stay organized:
+Use Projects to organize k6 tests in collections and grant access to these collections.
+Some ways to stay organized with Projects include the following:
 
-- Per team: Each team is given their own project for them to do their work and collaborate.
-- Per component: A project is created for each component or service you're testing.
-- Per brand: E-commerce customers may want to use projects per brand to stay organized.
-- Per customer: When dealing with custom software, you can to organize by customer to ensure each unique system is tested.
-- Per major release: After your systems go through a major change, you can to create a new project to organize the most recent data.
+- **Per team.** Each team is given their own project for them to do their work and collaborate.
+- **Per component.** A project is created for each component or service you're testing.
+- **Per brand.** E-commerce customers may want to use projects per brand to stay organized.
+- **Per customer.** When dealing with custom software, you can to organize by customer to ensure each unique system is tested.
+- **Per major release.** After your systems go through a major change, you can to create a new project to organize the most recent data.
 
 > To invite users to a project, refer to [manage project members]({{< relref "./manage-project-members" >}}).
 
 
 ## Running CLI Tests in a Specific Project
 
-By default, when you run a test from the CLI, the test runs in your default project. If you want to set the test run in a different project, specify the [`projectID` option]({{< relref "../author-run/cloud-scripting-extras/cloud-options" >}}) in the k6 script:
+By default, when you run a test from the CLI, the test runs in your default project.
+To set the test run in a different project, specify the [`projectID` option]({{< relref "../author-run/cloud-scripting-extras/cloud-options" >}}) in the k6 script:
 
 ```javascript
 export const options = {