Common use of Breach Capable of Cure Clause in Contracts

Breach Capable of Cure. In the event that either party (i) materially breaches any of its obligations hereunder, which breach is not cured within thirty (30) days after written notice is given to the breaching party specifying the breach or (ii) repeatedly breaches any of its obligations hereunder and fails to cure and cease committing such repeated breaches within thirty (30) days after being given written notice specifying the breaches, then the party not in breach may, by giving written notice thereof to the breaching party, terminate this Agreement, upon the expiration of a thirty (30)-day period beginning on the date of such notice of termination. Notwithstanding the foregoing, DTLA shall not terminate this Agreement for reason that a Robust Inactive Product manufactured or distributed by Adopter would not comply with the Compliance Rules if its DTCP functions were activated, provided that, no later than thirty (30) days after receiving notice of breach from DTLA, Adopter prevents activation of the DTCP functions of such Robust Inactive Product until such time, if any, that an Update is applied to such Robust Inactive Product that causes it to be a Licensed Product in accordance with the terms of Section 3.3.

Breach Capable of Cure. In the event that either party (i) materially breaches any of its obligations hereunder, which breach is not cured within thirty (30) days after written notice is given to the breaching party specifying the breach or (ii) repeatedly breaches any of its obligations hereunder and fails to cure and cease committing such repeated breaches within thirty (30) days after being given written notice specifying the breaches, then the party not in breach may, by giving written notice thereof to the breaching party, terminate this Agreement, upon the expiration of a thirty (30)-day period beginning on the date of such notice of termination. Notwithstanding the foregoing, DTLA shall not terminate this Agreement for reason that a Robust Inactive Product manufactured or distributed by Adopter would not comply with the Compliance Rules if its DTCP DTCP2 functions were activated, provided that, no later than thirty (30) days after receiving notice of breach from DTLA, Adopter prevents activation of the DTCP DTCP2 functions of such Robust Inactive Product until such time, if any, that an Update is applied to such Robust Inactive Product that causes it to be a Licensed Product in accordance with the terms of Section 3.3.

Breach Capable of Cure. In the event that either party (i) materially breaches any of its obligations hereunder, which breach is not cured within thirty (30) days after written notice is given to the breaching party specifying the breach or (ii) repeatedly breaches any of its obligations hereunder and fails to cure and cease committing such repeated breaches within thirty (30) days after being given written notice specifying the breaches, then the party not in breach may, by giving written notice thereof to the breaching party, terminate this Agreement, upon the expiration of a thirty (30)-day period beginning on the date of such notice of termination. Notwithstanding the foregoing, DTLA Licensor shall not terminate this Agreement for reason that a Robust Inactive Product manufactured or distributed by Adopter would not comply with the HDCP Specification, Compliance Rules or Robustness Rules if its DTCP functions it were activated, provided that, no later than thirty (30) days after receiving notice of breach from DTLALicensor, Adopter prevents activation of the DTCP HDCP functions of such Robust Inactive Product until such time, if any, that an Update is applied to such Robust Inactive Product that causes it to be a Licensed Product in accordance with the terms of Section 3.35.2.

Breach Capable of Cure. In the event that either party (i) materially breaches any of its obligations hereunder, which breach is not cured within thirty (30) days after written notice is given to the breaching party specifying the breach or (ii) repeatedly breaches any of its obligations hereunder and fails to cure and cease committing such repeated breaches within thirty (30) days after being given written notice specifying the breaches, then the party not in breach may, by giving written notice thereof to the breaching party, terminate this Agreement, upon the expiration of a thirty (30)-day period beginning on the date of such notice of termination. Notwithstanding the foregoing, DTLA Licensor shall not terminate this Agreement for reason that a Robust Inactive Product manufactured or distributed by Adopter would not comply with the HDCP Specification, Compliance Rules or Robustness Rules if its DTCP functions it were activated, provided that, no later than thirty (30) days after receiving notice of breach from DTLALicensor, Adopter prevents activation of the DTCP HDCP functions of such Robust Inactive Product until such time, if any, that an Update is applied to such Robust Inactive Product that causes it to be a Licensed Product in accordance with the terms of Section 3.3.5.2. For review only - Not valid for execution