docs: Tweak Cloud legalese (meltano#7504)

docs/src/_cloud/fees.md

@@ -19,7 +19,7 @@ Unless specified otherwise in the applicable Order Form, the following terms and
     - Base Spend: In a Credit Purchase, the base price charged for the credits covered by the Credit Threshold.
     - Credit Purchase: A nonrefundable upfront purchase of Credits in bulk.
     - Credit Threshold: The minimum Credit Purchase size to receive the rates on the Service Consumption Table below.
-    - Credit: A unit consumed by Pipeline Runs across the Organization. The number of Credits consumed by a given Pipeline Run is based on its Pipeline’s Frequency and its Additional Runtime. Credits can be purchased in bulk in a Credit Purchase, or be acquired as defined in the Service Level Agreement. Credits are shared by all Projects in an Organization, and may not be redeemed for cash.
+    - Credit: A unit consumed by Pipeline Runs across the Organization. The number of Credits consumed by a given Pipeline Run is based on its Pipeline’s Frequency and its Additional Runtime. Credits can be purchased in bulk in a Credit Purchase, or be acquired as set forth in the Service Level Agreement. Credits are shared by all Projects in an Organization, and may not be redeemed for cash.
     - Deployment: A deployment on Meltano Cloud of a specific Environment and Project Git repository branch combination.
     - Environment: An environment defined in the Project. An Environment may have multiple Schedules and Deployments.
     - Frequency: The number of times a Pipeline Run of a Schedule’s Pipeline is to be executed in a specific Deployment during a given period based on the Schedule’s cron schedule expression, with a maximum of one Run every 15 minutes.
@@ -33,13 +33,13 @@ Unless specified otherwise in the applicable Order Form, the following terms and
     - Organization: The Customer’s top-level entity on Meltano Cloud. An Organization may have multiple Projects.
     - Pipeline Run: An execution of a Pipeline.
     - Pipeline: A named pipeline defined in the Project, or the tasks associated with a Schedule.
-    - Project: A Git repository connected to the Organization containing a meltano.yml file and other artifacts created using Meltano Core. A Project may have multiple Pipelines, Schedules, Environments, and Deployments.
+    - Project: A Git repository containing a meltano.yml file and other artifacts created using Meltano Core that is accessed and used by Meltano Cloud. A Project may have multiple Pipelines, Schedules, Environments, and Deployments.
     - Runtime: The cumulative execution time of all tasks in a Pipeline Run, from the start of the task to the end of the task, excluding platform startup and shutdown time.
     - Schedule: A schedule defined in the Project and enabled in a specific Deployment.
 
-2. Credits are priced based on a diminishing slope: in other words, the more Pipelines you run, the cheaper the incremental cost per unique Pipeline Run. Rates will be determined by the Service Consumption Table set forth below, subject to the terms of your specific Order Form. Meltano will provide Customer with monthly usage for the current and previous months via the Meltano Cloud CLI and dashboard.
+2. Credits are priced based on a diminishing slope: in other words, the more Pipelines Customer runs, the cheaper the incremental cost per unique Pipeline Run. Rates will be determined by the Service Consumption Table set forth below, subject to the terms of your specific Order Form. Meltano will provide Customer with monthly usage for the current and previous months via the Meltano Cloud CLI and dashboard.
 
-3. When the Credits in Customer’s Organization are depleted, the Organization will no longer run Pipelines. When Credits are close to being depleted, Meltano Cloud will alert Customer. If Customer has a Credit Purchase that is coming to an end, Customer must contact their account representative to arrange for a new purchase on an updated Order Form, or complete a Credit Purchase through Meltano Cloud.‍
+3. When the Credits in Customer’s Organization are depleted, the Organization will no longer run Pipelines. When Credits are close to being depleted, Meltano Cloud will alert Customer. If Customer has a Credit Purchase that is coming to an end, Customer must contact Customer's account representative to arrange for a new purchase on an updated Order Form, or complete a Credit Purchase through Meltano Cloud.‍
 
 4. <u>Service Consumption Table</u>:
 

docs/src/_cloud/sla.md

@@ -17,7 +17,7 @@ Unless specified otherwise in the applicable Order Form, the following terms and
 1. <u>Definitions</u>:
     - Average Run Credits: The average number of Credits consumed by the Schedule’s most recent Consecutive Successful Runs.
     - Consecutive Successful Runs: 5 consecutive Successful Runs over at least 5 consecutive days since the last time the Pipeline’s configuration, or that of any of its tasks, was changed.
-    - Credit: A unit consumed by Pipeline Runs across the Organization. Credits can be purchased in bulk, or be acquired as defined in this agreement. Credits are shared by all Projects in an Organization, and may not be redeemed for cash.
+    - Credit: A unit consumed by Pipeline Runs across the Organization. Credits can be purchased in bulk, or be acquired as set forth in this Service Level Agreement. Credits are shared by all Projects in an Organization, and may not be redeemed for cash.
     - Deployment: A deployment on Meltano Cloud of a specific Environment and Project Git repository branch combination.
     - Downtime: Time that Schedules were not running as expected. Calculated as “Missed Ticks / Monthly Ticks” during a calendar month. The inverse of Uptime.
     - Emergency Maintenance: Downtime outside of Scheduled Downtime hours due to the application of urgent patches or fixes, or other urgent maintenance, recommended by Meltano’s vendors to be applied as soon as possible.
@@ -29,17 +29,17 @@ Unless specified otherwise in the applicable Order Form, the following terms and
     - Organization: The Customer’s top-level entity on Meltano Cloud. An Organization may have multiple Projects.
     - Pipeline Run: An execution of a Pipeline.
     - Pipeline: The tasks associated with a Schedule.
-    - Project: A Git repository connected to the Organization containing a meltano.yml file and other artifacts created using Meltano Core. A Project may have multiple Pipelines, Schedules, Environments, and Deployments.
+    - Project: A Git repository containing a meltano.yml file and other artifacts created using Meltano Core that is accessed and used by Meltano Cloud. A Project may have multiple Pipelines, Schedules, Environments, and Deployments.
     - Run: A Pipeline Run triggered as a result of a Tick.
     - Schedule: A schedule defined in the Project and enabled in a specific Deployment.
     - Scheduled Downtime: Downtime during the hours of 6:00 p.m. to 8:00 p.m. Thursday U.S. Pacific Time.
     - Successful Run: A Run that completed successfully, or that failed for a reason unrelated to the Meltano Cloud platform (e.g., misconfiguration or a source API issue).
     - Tick: Each time a Run of a Schedule’s Pipeline is to be executed in a specific Deployment based on its cron schedule expression, with a maximum of one Tick (and Run) every 15 minutes.
     - Trial Period: The period of time that Customer first has access to and uses Meltano Cloud for evaluation or trial without a paid contract in place as specified in the applicable agreement.
-    - Uptime: Time that Schedules were not as expected. Calculated as “(Monthly Ticks - Missed Ticks) / Monthly Ticks” during a past calendar month.
+    - Uptime: Time that Schedules were not running as expected. Calculated as “(Monthly Ticks - Missed Ticks) / Monthly Ticks” during a past calendar month.
     - Working Schedule: A Schedule that has had Consecutive Successful Runs.
 
-2. <u>Service Level Commitment and Credits</u>. If Uptime of a given Working Schedule falls below 99.9%, then for every Missed Tick of that Schedule, Customer’s Account shall be credited 2 times the Average Run Credits to be used by future Pipeline Runs. Credits given for Downtime may not exceed 50% of the Average Run Credits multiplied by the Schedule’s Monthly Ticks for the month in question.
+2. <u>Service Level Commitment and Credits</u>. If Uptime of a given Working Schedule falls below 99.9%, then for every Missed Tick of that Schedule, Customer’s Account shall be credited 2 times the Average Run Credits, which may be used solely for future Pipeline Runs. Credits given for Downtime may not exceed 50% of the Average Run Credits multiplied by the Schedule’s Monthly Ticks for the month in question and may not be redeemed for cash.
 
 3. <u>Exceptions</u>. The above service level commitment and Credits do not apply to Scheduled Maintenance or circumstances where the Cloud Service is affected by operational, connectivity or other service interruptions beyond Meltano’s sole control, including without limitation:
     - Maintenance requested by Customer or Emergency Maintenance;
@@ -53,7 +53,7 @@ Unless specified otherwise in the applicable Order Form, the following terms and
 
 4. <u>Exclusions</u>. The above service level commitment and Credits do not apply to any services or data that are not expressly listed in the CSA, whether implied or inferred, nor do they apply to performance issues caused by Customer's equipment or third-party equipment. The above service level commitment and Credits do not apply during a Trial Period.
 
-5. <u>Claiming Credits</u>. To receive any Credits, Customer must notify Meltano in writing within 30 days after Customer becomes eligible to receive a Credit. Failure to comply with this requirement will forfeit Client's right to receive a Credit.
+5. <u>Claiming Credits</u>. To receive any Credits, Customer must notify Meltano in writing within 30 days after Customer becomes eligible to receive a Credit. Failure to comply with this requirement will forfeit Customer's right to receive a Credit.
 
 6. <u>Limitations</u>. The remedies provided herein for interruptions in Cloud Service shall apply only while the Customer is in good standing and not in breach of any term of the Agreement, and the Customer accounts are paid in full with no amounts past due or security deposits not fully paid.