Upload 2 files

Update train and validation dataset

train.csv

@@ -11,7 +11,7 @@
 "If a claim under the applicable SLA is confirmed by us, then we will issue the Service Credit to you within one billing cycle following the month in which the request occurred.",0,OBLIGATION
 "If we confirm that the Monthly Uptime Percentage is less than the Service Commitment, we will issue the appropriate Service Credit to you within one billing cycle following the month in which we confirm your request.",0,OBLIGATION
 "IBM will validate SLA claims based upon information provided by Client and IBM system records and will notify Client of approved credits via the Cloud UI or email.",0,OBLIGATION
-"IBM's reasonable determination of a credit is final.",0,OBLIGATION
+"IBMs reasonable determination of a credit is final.",0,OBLIGATION
 "Client agrees to continue to make payment in full for Cloud Services while an SLA claim is being reviewed.",0,OBLIGATION
 "Client must submit an SLA claim by using the form at https://cloud.ibm.com/unifiedsupport/supportcenter within 60 days after the end of the calendar month that the service level was missed, providing sufficient.",0,OBLIGATION
 "Information to identify the affected service, error messages, and other information necessary to validate the claim, referencing IBM support tickets, as applicable.",0,OBLIGATION
@@ -54,7 +54,7 @@
 "But You may not recover Service Credits for such Cloud Service under multiple Service Level Agreements for the same incident.",0,OBLIGATION
 "But You may not recover Service Credits under multiple provisions for the same event (i.e., You may not recover Service Credits for such Cloud Service under both such order and this document for the same incident).",0,OBLIGATION
 "In no event may You receive more Service Credits than equate to the fees paid by You for the quantity of the applicable Non-Compliant Service that is actually used in the relevant Measured Period.",0,OBLIGATION
-"The Service Level Agreements for Cloud Services under this section (Oracle PaaS and IaaS Public Cloud Service Level Agreement Policy) are contingent on Your adherence to Oracle's recommended minimum technical configuration requirements for accessing and using the applicable Cloud Services from Your network infrastructure and Your user workstations as set forth in the Program Documentation for such Cloud Services.",0,OBLIGATION
+"The Service Level Agreements for Cloud Services under this section (Oracle PaaS and IaaS Public Cloud Service Level Agreement Policy) are contingent on Your adherence to Oracles recommended minimum technical configuration requirements for accessing and using the applicable Cloud Services from Your network infrastructure and Your user workstations as set forth in the Program Documentation for such Cloud Services.",0,OBLIGATION
 "With respect to a Cloud Service listed above for which the Manageability Service Level Agreement under this subsection applies, Oracle will use commercially reasonable efforts to have each such Service available with a Monthly Uptime Percentage (as defined below) of at least 99.9% during any calendar month (the “Service Commitment”)",0,OBLIGATION
 "With respect to a Cloud Service listed above for which the Availability Service Level Agreement under this subsection applies and that is deployed on shared or dedicated infrastructure with Autonomous Data Guard enabled (each a “Cloud Service with Autonomous Data Guard” and collectively the ""Cloud Services with Autonomous Data Guard""), Oracle will use commercially reasonable efforts to have each such Service available with a Monthly Uptime Percentage (as defined below) of at least 99.995% during any calendar month (the “Service Commitment”).",0,OBLIGATION
 "For Oracle Cloud Infrastructure - Ravello Service, the following applies in lieu of the text in section 4.1.1 of the Oracle Cloud Hosting and Delivery Policies: Oracle will work to provide prior notice for any emergency maintenance requiring a service interruption.",0,OBLIGATION
@@ -71,7 +71,7 @@
 "Customer must also provide Google with log files showing Downtime with respect to Encrypt, Decrypt, and/or Sign operations from the Covered Services and the date and time they occurred.",0,OBLIGATION
 "Financial Credits will be made in the form of a monetary credit applied to future use of the Covered Services and will be applied within 60 days after the Financial Credit was requested.",0,OBLIGATION
 "The Cloud Identity Covered Services interface will be operational and available to Customer at least 99.9% of the time in any calendar month.",0,OBLIGATION
-"In order to receive any of the Service Credits described above, Customer must notify Google (or, for Customers who ordered Services from a  Reseller, Customer may notify Reseller and Customer's Reseller must notify Google) within thirty days from the time Customer becomes eligible to receive a Service Credit.",0,OBLIGATION
+"In order to receive any of the Service Credits described above, Customer must notify Google (or, for Customers who ordered Services from a  Reseller, Customer may notify Reseller and Customers Reseller must notify Google) within thirty days from the time Customer becomes eligible to receive a Service Credit.",0,OBLIGATION
 "Service Credits may not be exchanged for, or converted to, monetary amounts, except for customers who are on  Google’s monthly billing plan.",0,OBLIGATION
 "The Covered Service will provide a Monthly Uptime Percentage of Serving DNS queries from at least one of the Google managed Authoritative Name Servers to Customer of 100%.",0,OBLIGATION
 "If Customer does not comply with these requirements, Customer will forfeit its right to receive a Financial Credit.",0,OBLIGATION
@@ -148,14 +148,14 @@
 "If at the end of the Services Period in which the WAF Services Credits were granted, You have any remaining unused WAF Service Credits, and You execute a replenishment order for the Funded Allocation Model, then such WAF Service Credits will be carried forward into the replenishment order’s Services Period, and subtracted from Your first invoice for Cloud Services acquired under such replenishment order.",1,RIGHT
 "The credit will be the highest applicable compensation based on the cumulative availability of the affected service during a contracted month and calculated using the monthly charges for such affected service.",1,RIGHT
 "In the event that availability of the Cloud Service during a contracted month is less than 99.95% the Client is eligible to receive a service level credit equal to an amount of 1% of the monthly charges for the selected subscription edition (including enabled additional components) for each cumulative whole hour of Downtime, up to a maximum of 20% per month.",1,RIGHT
-"For hourly subscriptions that incur an outage to running environments, the Client will receive an hour credit for the number of running VM's multiplied by the duration of the outage.",1,RIGHT
+"For hourly subscriptions that incur an outage to running environments, the Client will receive an hour credit for the number of running VMs multiplied by the duration of the outage.",1,RIGHT
 "Client is eligible for a credit as follows.",1,RIGHT
 "If the specified service level time period is not met, the client can receive a credit based on the monthly charge for the impacted service due to a hardware replacement or upgrade.",1,RIGHT
-"SLA credits are Client's exclusive remedy for IBM's failure to meet a specified service level.",1,RIGHT
+"SLA credits are Clients exclusive remedy for IBMs failure to meet a specified service level.",1,RIGHT
 "If Google does not meet the SLO, and if Customer meets its obligations under this SLA, Customer will be eligible to receive the Financial Credits described below.",1,RIGHT
-"This SLA states Customer's sole and exclusive remedy for any failure by Google to meet the SLO.",1,RIGHT
+"This SLA states Customers sole and exclusive remedy for any failure by Google to meet the SLO.",1,RIGHT
 "If Google  does not meet the Cloud Identity SLA, and if Customer meets its obligations under this Cloud Identity SLA, Customer will be eligible to receive the Service Credits described below.",1,RIGHT
-"This Cloud Identity SLA states Customer's sole and exclusive remedy for any failure by Google to meet  the Cloud Identity SLA.",1,RIGHT
+"This Cloud Identity SLA states Customers sole and exclusive remedy for any failure by Google to meet  the Cloud Identity SLA.",1,RIGHT
 "If Google does not meet the SLO, and if Customer meets its obligations under this SLA, Customer will be eligible to receive the Financial Credits described below.",1,RIGHT
 "This SLA states Customer’s sole and exclusive remedy for any failure by Google to meet the  SLO.",1,RIGHT
 "In the event that Google fails to meet the SLO, and provided the Customer has met all obligations under this SLA, they will be entitled to receive the Financial Credits outlined below.",1,RIGHT
@@ -163,34 +163,34 @@
 "If Google does not meet the SLO and the Customer complies with the requirements of this SLA, the Customer may be eligible to receive the Financial Credits described below.",1,RIGHT
 "For any failure by Google to meet the SLO, this SLA specifies the sole and exclusive solution available to the Customer.",1,RIGHT
 "Should Google fail to meet the SLO, and provided the Customer has fulfilled its obligations under this SLA, they will qualify to receive the Financial Credits as detailed below.",1,RIGHT
-"The sole and exclusive recourse available to the Customer for any failure on Google's part to meet the SLO is stated in this SLA.",1,RIGHT
+"The sole and exclusive recourse available to the Customer for any failure on Googles part to meet the SLO is stated in this SLA.",1,RIGHT
 "If Google is unable to meet the SLO, and the Customer has met its obligations under this SLA, they will be eligible to receive the Financial Credits explained below.",1,RIGHT
-"In the event of Google's failure to meet the SLO, this SLA specifies the Customer's exclusive remedy.",1,RIGHT
+"In the event of Googles failure to meet the SLO, this SLA specifies the Customers exclusive remedy.",1,RIGHT
 "In case Google fails to meet the SLO, the Customer may be eligible for the Financial Credits described below, subject to the Customer fulfilling their obligations under this SLA.",1,RIGHT
-"The Customer's only remedy for any failure by Google to meet the SLO is outlined in this SLA.",1,RIGHT
+"The Customers only remedy for any failure by Google to meet the SLO is outlined in this SLA.",1,RIGHT
 "If the Availability Percentage (as defined below) during a given month is less than 99.9%, a customer will be eligible for a credit as   provided below (“Service Credit”).",1,RIGHT
 "If the Availability of the specified service is less than the Availability Commitment, then you may request an SLA Credit.",1,RIGHT
 "If the AWS or GCP infrastructure is unavailable, and therefore the services are unavailable, your sole recourse pursuant to the Agreement is to us, and not to AWS or GCP.",1,RIGHT
 "If an SLA Event occurs for the NSX Advanced Load Balancer Hosted Controller Service, you are entitled to an SLA Credit proportional to the portion of capacity consumed by the impacted Hosted Controller.",1,RIGHT
 "If the Availability of a service is less than the associated Availability Commitment in a given billing  month, you may request an SLA Credit in accordance with the following table.",1,RIGHT
 "The Service Credits specified in this SLA are your sole and exclusive remedies for any SLA Events occurring during your subscription term for the Service Offering or for any other claim in connection with this SLA.",1,RIGHT
-"You may be eligible to receive an SLA Credit if the Service Offering's Availability falls short of the Availability Commitment.",1,RIGHT
+"You may be eligible to receive an SLA Credit if the Service Offerings Availability falls short of the Availability Commitment.",1,RIGHT
 "Your exclusive remedy, as per the Agreement, in case the AWS infrastructure becomes unavailable resulting in unavailability of the Service Offering, is with us and not with AWS.",1,RIGHT
 "You may have recourse to AWS pursuant to your separate agreement with AWS, which is required as provided in the Service Description, for any unavailability of the AWS systems.",1,RIGHT
-"In case the Service Offering's Availability is below the Availability Commitment for a billing month, you may request a single SLA Credit, along with an extra SLA Credit for every 300 additional minutes that the Service Offering was unavailable, limited to a maximum of three SLA Credits per billing month.",1,RIGHT
+"In case the Service Offerings Availability is below the Availability Commitment for a billing month, you may request a single SLA Credit, along with an extra SLA Credit for every 300 additional minutes that the Service Offering was unavailable, limited to a maximum of three SLA Credits per billing month.",1,RIGHT
 "The Service Credits specified in this SLA are your sole and exclusive remedies for any SLA Events occurring during your subscription term for the Service Offering or for any other claim in connection with this SLA.",1,RIGHT
 "You may be eligible to request an SLA Credit if the Availability of the Service Offering falls below the committed level.",1,RIGHT
 "If the AWS infrastructure is unavailable, and therefore the Service Offering is unavailable, your sole recourse pursuant to the Agreement is to us, and not to AWS.",1,RIGHT
 "We have recourse to AWS pursuant to our separate agreement with AWS.",1,RIGHT
 "You may have recourse to AWS pursuant to your separate agreement with AWS, which is required as provided in the Service Description, for any unavailability of the AWS systems.",1,RIGHT
-"In case the Service Offering's Availability falls below the committed level for a billing month, you can claim one SLA Credit, plus an extra one for every additional 300 minutes the service was unavailable, up to three SLA Credits per month.",1,RIGHT
+"In case the Service Offerings Availability falls below the committed level for a billing month, you can claim one SLA Credit, plus an extra one for every additional 300 minutes the service was unavailable, up to three SLA Credits per month.",1,RIGHT
 "Upon request, VMware will provide to you, within 45 days after a confirmed SLA Event, a copy of the Availability report that VMware makes generally available to customers.",1,RIGHT
 "The Service Credits outlined in this SLA are the only solutions available to you for any SLA incidents that arise during your service subscription period, or for any other claims related to this agreement.",1,RIGHT
 "In case the Service Offering fails to meet the Availability Commitment, you have the right to request an SLA Credit.",1,RIGHT
 "The Service Credits mentioned in this SLA are the only means of addressing any SLA events or complaints during the term of your Service Offering subscription or any other claims regarding this SLA.",1,RIGHT
 "Upon request, VMware will provide to you, within 45 days after a confirmed SLA Event, a copy of the Availability report that VMware makes generally available to customers.",1,RIGHT
 " If any SLA incidents occur during your subscription term for the Service Offering, or for any other claims related to this SLA, the only solutions available to you are the Service Credits outlined in this document.",1,RIGHT
-"Whenever the Service Offering's Availability falls short of the agreed level for a billing month, you have the option to request a maximum of three SLA Credits, with one credit for the first 300 minutes and an additional credit for each additional 300 minutes of unavailability.",1,RIGHT
+"Whenever the Service Offerings Availability falls short of the agreed level for a billing month, you have the option to request a maximum of three SLA Credits, with one credit for the first 300 minutes and an additional credit for each additional 300 minutes of unavailability.",1,RIGHT
 "The only recourse you have for any SLA events or claims related to this SLA during your subscription period is the Service Credits mentioned in this document.",1,RIGHT
 "You have the right to request an SLA Credit if the availability of the Service Component falls short of its associated Availability Commitment. Availability is computed based on the formula given below for each billing period.",1,RIGHT
 "If the Cloud Provider infrastructure is unavailable, and therefore the Service Offering   or the Service Component is unavailable, your sole recourse under this Service Level Agreement is to   us, and not to IBM or Microsoft (each a “Cloud Provider”).",1,RIGHT
@@ -217,7 +217,7 @@
 "(iii) that result from instances belonging to the Micro DB instance class or other instance classes which have similar CPU and memory resource limitations, (iv) that result from you not following the basic operational guidelines described in the Amazon Aurora User Guide (e.g., overloading a database instance to the point it is inoperable, creating an excessively large number of tables that significantly increases the recovery time, etc.), (v) caused by underlying database engine software that leads to repeated database crashes or an inoperable database instance.",2,NEITHER
 "IBM provides the following service level agreements (SLAs) for Cloud Services when IBM is listed as the Provider value in the IBM Cloud Catalog For 3rd party services, the SLA, if provided, will be set out in the 3rd party vendor terms for that service.",2,NEITHER
 "No credits will be due for failure to meet an SLA because of problems with: Client or community provided content, technology, designs, or instructions, non-IBM build-packs, unsupported system configurations and platforms.",2,NEITHER
-"Client infrastructure failures, including network, hardware, facility, or power, Client system administration actions, commands, or file transfers, Client errors or failures to provide needed information or access to resolve an outage, time to reload, configure, enable, or access content or include other services indirectly affected by an outage, Client-caused security incidents or Client security testing, or other causes beyond IBM's reasonable control.",2,NEITHER
+"Client infrastructure failures, including network, hardware, facility, or power, Client system administration actions, commands, or file transfers, Client errors or failures to provide needed information or access to resolve an outage, time to reload, configure, enable, or access content or include other services indirectly affected by an outage, Client-caused security incidents or Client security testing, or other causes beyond IBMs reasonable control.",2,NEITHER
 "Some services provide Client with infrastructure capabilities where Client is responsible for the implementation and management of said infrastructure",2,NEITHER
 "For such User-Managed Services, eligible downtime is limited to a disruption due to failures or planned maintenance involving any of the following: i) private or public network, ii) infrastructure power, or iii) HVAC infrastructure.",2,NEITHER
 "The Tier 1 SLA applies to most services and configurations not specified in a higher tier. This includes service plans where Client instantiates a single service instance that is hosted in a single data center.",2,NEITHER
@@ -231,7 +231,7 @@
 "Any failure of Client owned components when API calls are routed through Client owned components,   such as an API Gateway, that are paired with the IBM API Connect Dedicated offering do not count toward Downtime and are not eligible for SLA credit.",2,NEITHER
 "For Satellite-hosted services deployed on infrastructure not managed by IBM, the Tier 1 SLA applies, and unavailability attributed to infrastructure failures will not be counted in downtime calculations.",2,NEITHER
 "Errors are requests with a response code greater than or equal to 500.",2,NEITHER
-"Downtime is the total number of accrued minutes where every request made in a clock minute either returns an error or the instance is unavailable (as recorded by IBM's standard monitoring tools).",2,NEITHER
+"Downtime is the total number of accrued minutes where every request made in a clock minute either returns an error or the instance is unavailable (as recorded by IBMs standard monitoring tools).",2,NEITHER
 "For a Dedicated Cloudant Instance in IBM Cloud Dedicated, Downtime excludes any minute during which the request rate exceeds a peak of 500 requests per second.",2,NEITHER
 "In addition to the IBM Cloud Service Description, the Downtime definition specific to this Cloud Service is:   Downtime is the number of accrued minutes where every connection request to a database instance fails in a clock minute.",2,NEITHER
 "Service level time periods exclude any time required to reload the operating system or applications or time performance may be degraded.",2,NEITHER
@@ -276,7 +276,7 @@
 "Oracle PaaS and IaaS Public Cloud Services may be provisioned at multiple data centers, and depending   on product capability, availability, and customer solution design, You may be able to configure such Cloud Services with disaster recovery capabilities.",2,NEITHER
 "“VCN” is a customizable private network within the Oracle Cloud Infrastructure cloud.",2,NEITHER
 "This subsection (Service Credits) sets forth the terms regarding the grant to You of service credits   (“Service Credits”) under a Service Level Agreement set forth in this section (Oracle PaaS and IaaS Public   Cloud Service Level Agreement Policy) arising from Oracle’s failure to meet a Service Commitment with respect to an applicable Oracle PaaS or IaaS Public Cloud Service.",2,NEITHER
-"The grant of these Service Credits are YOUR EXCLUSIVE REMEDY AND ORACLE'S ENTIRE LIABILITY when Oracle has not met a Service Commitment for a Service Level Agreement under this section (Oracle PaaS and IaaS Public Cloud Service Level Agreement Policy)",2,NEITHER
+"The grant of these Service Credits are YOUR EXCLUSIVE REMEDY AND ORACLES ENTIRE LIABILITY when Oracle has not met a Service Commitment for a Service Level Agreement under this section (Oracle PaaS and IaaS Public Cloud Service Level Agreement Policy)",2,NEITHER
 "Service Credits will only be provided for the specific Cloud Service for which the applicable Service Commitment has not been met.",2,NEITHER
 "With the (i) percentage amount (the “Service Credit Percentage”) as set forth in the Service Commitment specified for such Cloud Service in this section (Oracle PaaS and IaaS Public Cloud Service Level Agreement Policy)",2,NEITHER
 "And (ii) the fees and usage based on the rate(s) and metric(s) set forth for such Cloud Service in Your order (pro-rated as necessary).",2,NEITHER

validation.csv

@@ -6,8 +6,8 @@
 "The credit request must include trouble ticket number(s) related to the  credit request.",0,OBLIGATION
 "Each request for credit in any calendar month must be received by NTTA within seven (7) days of the occurrence giving rise to the credit claim.",0,OBLIGATION
 "Each valid credit will be applied to a Customer invoice within two (2) billing cycles after NTTA’s receipt of such request.",0,OBLIGATION
-"NTTA's goal is to deliver SCD Content 100% of the time.",0,OBLIGATION
-"Subject to Sections 5 and 6 below, upon Customer's request, NTTA will issue a credit to Customer for SCD Service Outages in an amount equal to one day's worth of the Base Fee paid per affected Zone by Customer, multiplied by each 24-hour period in which Customer experiences a SCD Service Outage during a particular month.",0,OBLIGATION
+"NTTAs goal is to deliver SCD Content 100% of the time.",0,OBLIGATION
+"Subject to Sections 5 and 6 below, upon Customers request, NTTA will issue a credit to Customer for SCD Service Outages in an amount equal to one days worth of the Base Fee paid per affected Zone by Customer, multiplied by each 24-hour period in which Customer experiences a SCD Service Outage during a particular month.",0,OBLIGATION
 "NTTA will periodically (on average every 15 minutes) measure SCD availability by requesting representative Cacheable Objects from Cache Servers at Selected POPs using software and hardware components capable of measuring traffic and responses at such Selected POPs.",0,OBLIGATION
 "Customers must store the health check content on the folder that NTT Communications specified on the customer’s origin server.",0,OBLIGATION
 "To be eligible for compensation under this SLA, the Customer must initiate a problem report by opening a support ticket and request a resolution to the issue.",0,OBLIGATION
@@ -19,15 +19,15 @@
 "NTTA will issue a credit when the cumulative Service Outage exceeds three (3) hours and thirty-six  (36) minutes of downtime (equivalent to 99.5%) in a calendar month for those customers that have  NTTA managed HBAs.",0,OBLIGATION
 "For those customers that own their HBA, NTTA will issue a credit when the  cumulative Service Outage exceeds seven (7) hours and twelve (12) minutes of downtime (equivalent to 99%) in a calendar month.",0,OBLIGATION
 "To qualify for a credit as per this SLA, the customer must initiate a trouble ticket to report and seek resolution for the issue.",0,OBLIGATION
-"The credit request must  include trouble ticket number(s) related to the credit request. Each credit request in connection with  this SLA must be received by NTTA within 48 hours of the support failure referenced in Section 1  above and must include the Customer's account number (per NTTA's invoice), Customer's name as listed on NTTA's invoice, the date and approximate time of the support failure, and the SAN identification code or the server identification code(s) of the affected server(s) if applicable.",0,OBLIGATION
+"The credit request must  include trouble ticket number(s) related to the credit request. Each credit request in connection with  this SLA must be received by NTTA within 48 hours of the support failure referenced in Section 1  above and must include the Customers account number (per NTTAs invoice), Customers name as listed on NTTAs invoice, the date and approximate time of the support failure, and the SAN identification code or the server identification code(s) of the affected server(s) if applicable.",0,OBLIGATION
 "NTTA’s Virtualization Services’ Availability SLA offers a 99.9% uptime guarantee related to the Data Center Facilities, Network Infrastructure and VM Cluster within the Customer’s solution as outlined below that are deployed in NTTA data centers in the United States.",0,OBLIGATION
 "This SLA guarantees the availability of the VM Cluster but not the individual nodes of the VM Cluster.",0,OBLIGATION
 "NTTA does not guarantee the availability of the specific VM instances and are considered out of scope of this SLA.",0,OBLIGATION
 "Customer solutions must be configured with redundant, high availability (HA) Firewalls and Load Balancers to be eligible for credits under this SLA.",0,OBLIGATION
 "NTTA will monitor each ESX server in a VM Cluster via ICMP (PING) between NTTA’s Monitoring System and the Customer solution.",0,OBLIGATION
-"NTTA will issue a credit for any unique Service Outage that exceeds forty-three (43) minutes of downtime, in an amount equal to one day's worth of the total Monthly Recurring Charge (MRC) for those components that make up the VM Cluster paid by Customer during a calendar month, based on a thirty (30) day month.",0,OBLIGATION
+"NTTA will issue a credit for any unique Service Outage that exceeds forty-three (43) minutes of downtime, in an amount equal to one days worth of the total Monthly Recurring Charge (MRC) for those components that make up the VM Cluster paid by Customer during a calendar month, based on a thirty (30) day month.",0,OBLIGATION
 "The request for credit must contain the relevant trouble ticket number(s) associated with the request.",0,OBLIGATION
-"The credit request must include trouble ticket number(s) related to the credit request. Each credit request in connection with this SLA must be received by NTTA within 48 hours of the support failure referenced in Section 1 above and must include the Customer's customer number (per NTTA's invoice), Customer's name as listed on NTTA's invoice, the date and approximate time of the support failure, and the server identification code(s) of the affected server(s).",0,OBLIGATION
+"The credit request must include trouble ticket number(s) related to the credit request. Each credit request in connection with this SLA must be received by NTTA within 48 hours of the support failure referenced in Section 1 above and must include the Customers customer number (per NTTAs invoice), Customers name as listed on NTTAs invoice, the date and approximate time of the support failure, and the server identification code(s) of the affected server(s).",0,OBLIGATION
 "We shall use commercially reasonable endeavors to provide (1) Instance Monthly Uptime Percentage of Instance Unavailable for no less than 99.975% of each calendar month and (2) Instance Monthly Uptime Percentage of Multi-zone Service Unavailable for no less than 99.995% of each calendar month in connection with your use of the Service (the “Service Guarantee”).",0,OBLIGATION
 "Your claim must include at least the following information: A detailed description of the incident, including the logs or messages for request failure documenting the errors and claimed outage.",0,OBLIGATION
 "Your claim for a Service Credit can be filed starting from the sixth working days of the following calendar month of occurrence of the event giving rise to the claim must be received by us within sixty (60) days after the last day of the calendar month of occurrence of the event giving rise to the claim.",0,OBLIGATION
@@ -103,7 +103,7 @@
 "The process to present the Snapshot to the remote servers at the secondary data center will start within 1 hour of the Customer contacting NTTA’s CEC requesting that the Snapshot be presented.",1,RIGHT
 "As the Customer’s sole and exclusive remedy for such failure, Customer will receive a credit equal to one day’s worth of the total recurring monthly fees paid by Customer to NTTA for the applicable calendar month for NTTA Remote Data Replication Service.",1,RIGHT
 "The failover process of the Customer’s environment at the secondary data center will begin within 1 hour of the Customer notifying the NTTA CEC that   they have validated the snapshot.",1,RIGHT
-"The Customer will be compensated for any failure with a credit equal to one day's worth of their monthly fees paid to NTTA for their Remote Data Replication Service.",1,RIGHT
+"The Customer will be compensated for any failure with a credit equal to one days worth of their monthly fees paid to NTTA for their Remote Data Replication Service.",1,RIGHT
 "Customer shall not receive any credits under this SLA in connection with any failure of deficiency of the NTTA Remote Data Replication Service or a failure to meet the SLA that is caused by or associated with any of the following",1,RIGHT
 "Customer may then make a credit request by submitting a billing ticket via the NTT America Enterprise Hosting Customer Portal located at us.portal.ntt.net.",1,RIGHT
 "Notwithstanding  anything in this SLA to the contrary, the total amount credited to a Customer in connection  with Replication, Snapshot Access and Failover in any calendar month will not exceed, in the aggregate, one hundred percent (100%) of the total recurring monthly fee paid by Customer to NTTA for the NTTA Remote Data Replication Service for such calendar month.",1,RIGHT
@@ -187,11 +187,11 @@
 "If Verizon fails to meet the Network Packet Delivery Service Level in any given month, the Customer can request a credit for that month.",1,RIGHT
 "If Verizon is unable to meet the Jitter Service Level for North America in a given month, the Customer may request a credit for that month.",1,RIGHT
 "Verizon reserves the right to perform maintenance outside of Scheduled Maintenance during an emergency situation.",1,RIGHT
-"If there is a cumulative hour of Data Center Internet Bandwidth Unavailability or a fraction thereof in any given month, the Customer can request a credit for one day of Data Center Internet Band width monthly recurring charges as agreed upon in the Customer's Data Center Colocation/Internet Colocation agreement.",1,RIGHT
+"If there is a cumulative hour of Data Center Internet Bandwidth Unavailability or a fraction thereof in any given month, the Customer can request a credit for one day of Data Center Internet Band width monthly recurring charges as agreed upon in the Customers Data Center Colocation/Internet Colocation agreement.",1,RIGHT
 "The Outage Reporting SLA is applicable only to service provided in the contiguous United States and is applicable only if a Customer sets up his IP addresses for monitoring through https://clientcentral.verizonbusiness.com.",1,RIGHT
 "If Verizon fails to meet the Outage Reporting Service Level, Customer may request a credit for one day of the Monthly recurring charges for the affected Data Center Internet Band width and Data Center Colocation/Internet Colocation space only.",1,RIGHT
-"In case Verizon fails to restore data from tape to the customer's primary storage space in the same condition as backed up, the customer can claim a service credit equal to a percentage of the monthly recurring backup charges, as indicated in the table below.",1,RIGHT
-"If Verizon does not meet the Denial of Service Response SLA in any given month, the customer can request a credit for one day's charge of the Data Center Internet Band width service linked with the customer's Data Center Colocation/Internet Colocation agreement.",1,RIGHT
+"In case Verizon fails to restore data from tape to the customers primary storage space in the same condition as backed up, the customer can claim a service credit equal to a percentage of the monthly recurring backup charges, as indicated in the table below.",1,RIGHT
+"If Verizon does not meet the Denial of Service Response SLA in any given month, the customer can request a credit for one days charge of the Data Center Internet Band width service linked with the customers Data Center Colocation/Internet Colocation agreement.",1,RIGHT
 "Verizon will use trouble tickets and other appropriate Verizon records to determine, in its sole judgment, SLA  compliance.",1,RIGHT
 "Maintenance Events. From time to time, Linode may perform repairs, replacements, upgrades, updates,  patches, fixes, or other maintenance which may delay, disrupt, suspend, or otherwise affect a Covered  Service (each a “Maintenance Event”).",1,RIGHT
 "Linode will use reasonable efforts to attempt to minimize the impact of Maintenance Events, but shall have sole discretion in determining the need for, and scope of, any  Maintenance Event.",1,RIGHT
@@ -203,20 +203,20 @@
 "For the purposes of this SLA, any applicable credits would be based on the monthly fee paid by Customer for the storage which is deployed solely for the purposes of replication at both the primary and secondary sites as well as any stand-by servers utilized solely for the purposes of enabling failover as part of the NTTA Remote Data Replication solution.",2,NEITHER
 "Subject to Sections 2, 3 and 4 hereof, for each day in each calendar month during the Term in which NTTA fails to provide Snapshot access to the replicated data in accordance with clause B(i) above.",2,NEITHER
 "Failure of Customer to maintain NTTA SAN specific settings. For Colocation Customers, failure to maintain current required Version of the software in support of the Service and failure of software due to conflict with other non-compatible software.",2,NEITHER
-"DNS issues outside the direct control of NTTA. Any other acts or omissions of Customer or others authorized by Customer, including without limitation, any negligence, willful misconduct, or use of the NTTA Network or NTTA services in breach of NTTA's Terms and Conditions and Acceptable Use Policy.",2,NEITHER
+"DNS issues outside the direct control of NTTA. Any other acts or omissions of Customer or others authorized by Customer, including without limitation, any negligence, willful misconduct, or use of the NTTA Network or NTTA services in breach of NTTAs Terms and Conditions and Acceptable Use Policy.",2,NEITHER
 "The NTTA Remote Data Replication Service is not intended to be a comprehensive disaster recovery solution.",2,NEITHER
 "This NTT America (NTTA) Smart Content DeliveryTM Service Level Agreement (SLA) provides Customers with certain rights and remedies regarding NTTA’s Smart Content Delivery (“SCD”) performance.",2,NEITHER
 "This NTTA SCD SLA applies only to SCD Customers and applies only to the SCD portion of the Services that Customer receives from NTTA.",2,NEITHER
 "Availability is based on caching service being available from the zones for which the customer has contracted.",2,NEITHER
-"Customer's acts or omissions (or act or omissions of others engaged or authorized by Customer), including without limitation, any negligence, willful misconduct, or use of the NTTA services in breach of NTTA's Terms and Conditions of Service or NTTA's Acceptable Use Policy.",2,NEITHER
+"Customers acts or omissions (or act or omissions of others engaged or authorized by Customer), including without limitation, any negligence, willful misconduct, or use of the NTTA services in breach of NTTAs Terms and Conditions of Service or NTTAs Acceptable Use Policy.",2,NEITHER
 "If a zone’s test result does not meet the guaranteed standards by the measurement methodology stipulated in the course of a day",2,NEITHER
 "This is the base charge and minimum commitment data transfer charge and option services charge.",2,NEITHER
 "The subject services are the following: i. Basic Cache monthly charge  ii. Committed data transfer charge  iii. Additional Global DNS service monthly charge",2,NEITHER
 "The credit is added up accordingly, but credit given cannot exceed the total monthly charge.",2,NEITHER
 "As used herein, “Availability” means the ability of Customer to access, based on the line of demarcation defined as the customer’s Host Bus Adapter (HBA), each allocated LUN containing the Customer’s data and information stored on the NTTA SAN infrastructure.",2,NEITHER
 "Any Service Outage less than five (5) consecutive minutes will not be counted toward the aggregate total downtime for any given month.",2,NEITHER
-"Customers shall not receive any credits under this SLA in connection with any failure of NTT America's operations group to resolve a problem caused by or associated with Circumstances beyond NTT America's reasonable control, including, without limitation: acts of any governmental body, war, insurrection, sabotage, embargo, fire, flood, strike, or other labor disturbance, interruption of or delay in transportation.",2,NEITHER
-"The credit amount will be equal to one day's worth of the   total Monthly Recurring Charge (MRC) for those components that make up the SAN solution paid by Customer during a calendar month, based on a thirty (30) day month.",2,NEITHER
+"Customers shall not receive any credits under this SLA in connection with any failure of NTT Americas operations group to resolve a problem caused by or associated with Circumstances beyond NTT Americas reasonable control, including, without limitation: acts of any governmental body, war, insurrection, sabotage, embargo, fire, flood, strike, or other labor disturbance, interruption of or delay in transportation.",2,NEITHER
+"The credit amount will be equal to one days worth of the   total Monthly Recurring Charge (MRC) for those components that make up the SAN solution paid by Customer during a calendar month, based on a thirty (30) day month.",2,NEITHER
 "Availability of 99.9% for Virtualization Services equates to an aggregated 43.2 minutes of downtime within a calendar month.",2,NEITHER
 "A Service Outage is defined as a “disruption in Service” that lasts five (5) consecutive minutes or more where the Customer notifies NTTA of the outage or if NTTA receives an outage notification via its monitoring system.",2,NEITHER
 "Data Center Facilities availability refers to any disruption of Service related to power and/or cooling.",2,NEITHER
@@ -298,4 +298,4 @@
 "4.1 any system maintenance with prior notice by Tencent Cloud to a client, including system cutover, maintenance, upgrade and failure simulation test.",2,NEITHER
 "You may review the most updated version of relevant Agreement terms on the official website of Tencent Cloud.",2,NEITHER
 "As an ancillary agreement to the Tencent Cloud Service Agreement, this Agreement is of the same legal effect as the Tencent Cloud Service Agreement.",2,NEITHER
-"Each month's Network performance statistics relating to the Network Jitter SLAs for North America will be posted to the following location: http://www.verizonbusiness.com/about/network/latency/.",2,NEITHER
+"Each months Network performance statistics relating to the Network Jitter SLAs for North America will be posted to the following location: http://www.verizonbusiness.com/about/network/latency/.",2,NEITHER