AMENDMENTS, MODIFICATIONS AND WAIVERS WITH RESPECT TO CREDIT DOCUMENTS Sample Clauses

AMENDMENTS, MODIFICATIONS AND WAIVERS WITH RESPECT TO CREDIT DOCUMENTS. Any amendment or modification of, or waiver of compliance with the terms of any Credit Document, shall (subject to subsection 7.1(c)) be subject to the following requirements: (a) Until (i) the termination of the Term Loan Agreement and the Payment in Full of all Term Loan Obligations, without the prior written consent of Requisite Term Loan Lenders, and (ii) the termination of the Revolver Credit Agreement and the Payment in Full of all Revolver Loan Obligations, without the prior written consent of Requisite Revolver Lenders, Company shall not, and shall not permit any of its Subsidiaries to amend, restate, modify or waive (or make any payment consistent with an amendment, restatement, modification or waiver of) any material provision of the Management Services and Reimbursement Agreement, the Existing IPP Project Guaranties, or the DHC Tax Sharing Agreement, in each case if the effect of such amendment, restatement, modification or waiver, together with all other amendments, restatements, modifications or waivers made, (a) is to impose additional material obligations on, or confer additional material rights to the holders thereof (or to other obligees with respect thereto) against, Company or any of its Subsidiaries, (b) is otherwise adverse to the interests of the Term Loan Lenders in a manner deemed material in the judgment of the Term Loan Agents or Requisite Term Loan Lenders so notifying Term Loan Agents or Company, or (c) is otherwise adverse to the interests of the Revolver Lenders in a manner deemed material in the judgment of the Revolver Agent or Requisite Revolver Lenders so notifying Revolver Agent or Company. (b) Subject to the provisions of subsection 2.4, and until the termination of the Term Loan Agreement and the Payment in Full of all Term Loan Obligations, without the prior written consent of Requisite Term Loan Lenders, Revolver Lenders may not amend, restate, modify or waive (or receive any payment consistent with an amendment, restatement, modification or waiver of) any material provision of any of the Revolver Documents, unless (i) the terms of the Revolver Documents as so amended, restated, modified or waived are not more disadvantageous to Company and its Subsidiaries and the Term Loan Lenders (in a manner deemed material by Term Loan Agent or Requisite Term Loan Lenders so notifying Term Loan Agent or Company) than the Revolver Documents in effect on the Closing Date (it being understood and agreed that any amendment, restateme...
Sample 1Sample 2See All (4)
AutoNDA by SimpleDocs

Related to AMENDMENTS, MODIFICATIONS AND WAIVERS WITH RESPECT TO CREDIT DOCUMENTS

  • Amendments, Modifications and Waivers No amendment, modification or waiver in respect of this Agreement shall be effective against any party unless it shall be in writing and signed by Parent, the Company and Stockholder.

  • Modifications, Amendments and Waivers This Agreement may not be modified or amended, or any provision thereof waived, except in a writing signed by all the parties to this Agreement.

  • Amendments; Waivers; Modifications This Security Agreement and the provisions hereof may not be amended, waived, modified, changed, discharged or terminated except as set forth in Section 9.1 of the Credit Agreement.

  • Modifications and Waivers No provision of this Agreement shall be modified, waived or discharged unless the modification, waiver or discharge is agreed to in writing and signed by the Executive and by an authorized officer of the Company (other than the Executive). No waiver by either party of any breach of, or of compliance with, any condition or provision of this Agreement by the other party shall be considered a waiver of any other condition or provision or of the same condition or provision at another time.

  • Amendments and Waivers (a) If the ICANN Board of Directors determines that an amendment to this Agreement (including to the Specifications referred to herein) and all other registry agreements between ICANN and the Applicable Registry Operators (the “Applicable Registry Agreements”) is desirable (each, a “Special Amendment”), ICANN may adopt a Special Amendment pursuant to the requirements of and process set forth in this Section 7.6; provided that a Special Amendment may not be a Restricted Amendment. (b) Prior to submitting a Special Amendment for Registry Operator Approval, ICANN shall first consult in good faith with the Working Group regarding the form and substance of such Special Amendment. The duration of such consultation shall be reasonably determined by ICANN based on the substance of the Special Amendment. Following such consultation, ICANN may propose the adoption of a Special Amendment by publicly posting such amendment on its website for no less than thirty (30) calendar days (the “Posting Period”) and providing notice of such proposed amendment to the Applicable Registry Operators in accordance with Section 7.9. ICANN will consider the public comments submitted on a Special Amendment during the Posting Period (including comments submitted by the Applicable Registry Operators). (c) If, within one hundred eighty (180) calendar days following the expiration of the Posting Period (the “Approval Period”), the ICANN Board of Directors approves a Special Amendment (which may be in a form different than submitted for public comment, but must address the subject matter of the Special Amendment posted for public comment, as modified to reflect and/or address input from the Working Group and public comments), ICANN shall provide notice of, and submit, such Special Amendment for approval or disapproval by the Applicable Registry Operators. If, during the sixty (60) calendar day period following the date ICANN provides such notice to the Applicable Registry Operators, such Special Amendment receives Registry Operator Approval, such Special Amendment shall be deemed approved (an “Approved Amendment”) by the Applicable Registry Operators, and shall be effective and deemed an amendment to this Agreement on the date that is sixty (60) calendar days following the date ICANN provided notice of the approval of such Approved Amendment to Registry Operator (the “Amendment Effective Date”). In the event that a Special Amendment does not receive Registry Operator Approval, the Special Amendment shall be deemed not approved by the Applicable Registry Operators (a “Rejected Amendment”). A Rejected Amendment will have no effect on the terms and conditions of this Agreement, except as set forth below. (d) If the ICANN Board of Directors reasonably determines that a Rejected Amendment falls within the subject matter categories set forth in Section 1.2 of Specification 1, the ICANN Board of Directors may adopt a resolution (the date such resolution is adopted is referred to herein as the “Resolution Adoption Date”) requesting an Issue Report (as such term is defined in ICANN’s Bylaws) by the Generic Names Supporting Organization (the “GNSO”) regarding the substance of such Rejected Amendment. The policy development process undertaken by the GNSO pursuant to such requested Issue Report is referred to herein as a “PDP.” If such PDP results in a Final Report supported by a GNSO Supermajority (as defined in ICANN’s Bylaws) that either (i) recommends adoption of the Rejected Amendment as Consensus Policy or (ii) recommends against adoption of the Rejected Amendment as Consensus Policy, and, in the case of (i) above, the Board adopts such Consensus Policy, Registry Operator shall comply with its obligations pursuant to Section 2.2 of this Agreement. In either case, ICANN will abandon the Rejected Amendment and it will have no effect on the terms and conditions of this Agreement. Notwithstanding the foregoing provisions of this Section 7.6(d), the ICANN Board of Directors shall not be required to initiate a PDP with respect to a Rejected Amendment if, at any time in the twelve (12) month period preceding the submission of such Rejected Amendment for Registry Operator Approval pursuant to Section 7.6(c), the subject matter of such Rejected Amendment was the subject of a concluded or otherwise abandoned or terminated PDP that did not result in a GNSO Supermajority recommendation. (e) If (a) a Rejected Amendment does not fall within the subject matter categories set forth in Section 1.2 of Specification 1, (b) the subject matter of a Rejected Amendment was, at any time in the twelve (12) month period preceding the submission of such Rejected Amendment for Registry Operator Approval pursuant to Section 7.6(c), the subject of a concluded or otherwise abandoned or terminated PDP that did not result in a GNSO Supermajority recommendation, or (c) a PDP does not result in a Final Report supported by a GNSO Supermajority that either (A) recommends adoption of the Rejected Amendment as Consensus Policy or (B) recommends against adoption of the Rejected Amendment as Consensus Policy (or such PDP has otherwise been abandoned or terminated for any reason), then, in any such case, such Rejected Amendment may still be adopted and become effective in the manner described below. In order for the Rejected Amendment to be adopted, the following requirements must be satisfied: (i) the subject matter of the Rejected Amendment must be within the scope of ICANN’s mission and consistent with a balanced application of its core values (as described in ICANN’s Bylaws); (ii) the Rejected Amendment must be justified by a Substantial and Compelling Reason in the Public Interest, must be likely to promote such interest, taking into account competing public and private interests that are likely to be affected by the Rejected Amendment, and must be narrowly tailored and no broader than reasonably necessary to address such Substantial and Compelling Reason in the Public Interest; (iii) to the extent the Rejected Amendment prohibits or requires conduct or activities, imposes material costs on the Applicable Registry Operators, and/or materially reduces public access to domain name services, the Rejected Amendment must be the least restrictive means reasonably available to address the Substantial and Compelling Reason in the Public Interest; (iv) the ICANN Board of Directors must submit the Rejected Amendment, along with a written explanation of the reasoning related to its determination that the Rejected Amendment meets the requirements set out in subclauses (i) through (iii) above, for public comment for a period of no less than thirty (30) calendar days; and (v) following such public comment period, the ICANN Board of Directors must (a) engage in consultation (or direct ICANN management to engage in consultation) with the Working Group, subject matter experts, members of the GNSO, relevant advisory committees and other interested stakeholders with respect to such Rejected Amendment for a period of no less than sixty (60) calendar days; and (b) following such consultation, reapprove the Rejected Amendment (which may be in a form different than submitted for Registry Operator Approval, but must address the subject matter of the Rejected Amendment, as modified to reflect and/or address input from the Working Group and public comments) by the affirmative vote of at least two-­‐thirds of the members of the ICANN Board of Directors eligible to vote on such matter, taking into account any ICANN policy affecting such eligibility, including ICANN’s Conflict of Interest Policy (a “Board Amendment”). Such Board Amendment shall, subject to Section 7.6(f), be deemed an Approved Amendment, and shall be effective and deemed an amendment to this Agreement on the date that is sixty (60) calendar days following the date ICANN provided notice of the approval of such Board Amendment to Registry Operator (which effective date shall be deemed the Amendment Effective Date hereunder). Notwithstanding the foregoing, a Board Amendment may not amend the registry fees charged by ICANN hereunder, or amend this Section 7.6. (f) Notwithstanding the provisions of Section 7.6(e), a Board Amendment shall not be deemed an Approved Amendment if, during the thirty (30) calendar day period following the approval by the ICANN Board of Directors of the Board Amendment, the Working Group, on the behalf of the Applicable Registry Operators, submits to the ICANN Board of Directors an alternative to the Board Amendment (an “Alternative Amendment”) that meets the following requirements: (i) sets forth the precise text proposed by the Working Group to amend this Agreement in lieu of the Board Amendment; (ii) addresses the Substantial and Compelling Reason in the Public Interest identified by the ICANN Board of Directors as the justification for the Board Amendment; and (iii) compared to the Board Amendment is: (a) more narrowly tailored to address such Substantial and Compelling Reason in the Public Interest, and (b) to the extent the Alternative Amendment prohibits or requires conduct or activities, imposes material costs on Affected Registry Operators, or materially reduces access to domain name services, is a less restrictive means to address the Substantial and Compelling Reason in the Public Interest. Any proposed amendment that does not meet the requirements of subclauses (i) through

  • Modifications and Amendments The terms and provisions of this Agreement may be modified or amended only by written agreement executed by all parties hereto.

  • Specific Amendments to Credit Agreement Upon the effectiveness of this Amendment, the parties hereto agree that the Credit Agreement shall be amended as follows: (a) The Credit Agreement is amended by adding the following definitions to Section 1.01 thereof in the appropriate alphabetical location:

  • Amendments to Credit Agreement (a) Section 1.01 of the Credit Agreement is hereby amended by adding the following definitions in the appropriate alphabetical order:

  • Modifications; Amendments; Waivers The terms and provisions of this Agreement may not be modified or amended, nor may any provision be waived, except pursuant to a writing signed by the Corporation and the holders of at least a majority of the Registrable Shares then outstanding.

  • Amendments, Waivers, Etc This Agreement may not be amended, changed, supplemented, waived or otherwise modified or terminated, except upon the execution and delivery of a written agreement executed by the parties hereto.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!