Modifications and updates Sample Clauses
The "Modifications and Updates" clause defines the process by which changes to the agreement or its terms can be made after the contract is signed. Typically, this clause outlines who has the authority to make modifications, the required method for communicating updates (such as written notice or mutual agreement), and whether consent from all parties is necessary. Its core practical function is to ensure that any alterations to the contract are handled transparently and with proper documentation, thereby preventing misunderstandings or disputes about the validity of changes.
Modifications and updates. DES reserves the right to modify this agreement at any time; provided, however, that the terms and conditions of the then-current agreement will be posted on the DES website; and, provided further, that any company may opt out of the program at any time by sending notice to ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇@▇▇▇.▇▇.▇▇▇. Any company may update its company information and technical service categories by providing a new agreement to ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇@▇▇▇.▇▇.▇▇▇.
Modifications and updates. Licensor in its sole discretion shall be entitled, but not obliged, to create updates of the Software and, if Licensor decides to do so, to make them available to the Licensee against separate remuneration.
Modifications and updates. PlanSource may on one or more occasions modify or update this EUSA. PlanSource will post notices of EUSA modifications or updates through links placed on the PlanSource website or login pages or provide notification by other means. Please review this EUSA periodically for modifications or updates. If End User uses the Services after PlanSource posts any modifications or updates, End User will be deemed as having accepted them. If End User does not agree to any modified or updated terms of the EUSA or changes to other PlanSource policies, End User should discontinue its use of the Services, and this will be End User’s sole and exclusive remedy. If there is a conflict between this EUSA and the most current version of this EUSA posted on the PlanSource website, login pages, or otherwise provided to End User, the most current version will prevail.
Modifications and updates. Weisang is entitled to develop Software updates at its own discretion. Weisang is not obligated to make updates of this Software available to Licensees who have not entered into a maintenance agreement or have not acquired an update.
Modifications and updates. The Licensor is entitled to make modifications and extensions to the Software at its own discretion. The Licensee shall not have the right to have any modification or update carried out.
Modifications and updates. We reserve the right to modify, suspend or discontinue, temporarily or permanently, the Service or any related service to which it connects, with or without notice and without liability to you. From time to time we may provide changes, enhancements or improvements to the features/functionality of the Service, which may include patches, bug fixes, updates, upgrades, changes, removals and other modifications ("Changes"). Changes may add, modify or delete certain features and/or functionalities of the Service. You agree that we have no obligation to (a) provide any Changes, or (b) continue to provide or enable any features and/or functionalities of the Service to you. You further agree that all Changes will be (a) deemed to constitute an integral part of the Service, and (b) subject to the terms and conditions of this Agreement.
Modifications and updates. A. Section 3.B. of the UAA is hereby amended by deleting the first sentence of such section and replacing it with the following sentence: “Developer has received Town approval of a Master Plan, with case number ZMA-7-16, as amended by Town of Knightdale Ordinance #▇▇- ▇▇-▇▇-▇▇▇, with case number ZMA-8-19, as amended by Town of Knightdale Ordinance #23-02- 15-004, with case number ZMA-15-21.”
B. Exhibit B attached to the UAA is hereby amended to delete Sheet C2.0 and replace it with Sheet C2.0 attached to this Amendment on Exhibit B. All references in the UAA to Sheet C2.0 of the Master Plan shall refer to Sheet C2.0 of Exhibit B attached to this Amendment.
C. Exhibit C attached to the UAA is hereby deleted and replaced with Exhibit C attached to this Amendment. The Town hereby acknowledges that the requirements in Section 1, Section 2, Section 3.a. and Section 3.b. of the Phasing Schedule have been completed by Developer.
D. Exhibit E attached to the UAA and labelled Open Space Plan is hereby amended to delete Sheet L2.0 and replace it with Sheet L2.0 attached to this Amendment on Exhibit E. All references in the UAA to Sheet L2.0 of the Master Plan shall refer to Sheet L2.0 of Exhibit E attached to this Amendment.
E. The Planned Unit Development document entitled ▇▇▇▇▇▇ Parkstone Planned Unit Development approved in connection with the adoption of Town of Knightdale Ordinance #▇▇- ▇▇-▇▇-▇▇▇ (approving zoning application ZMA-15-21 with certain conditions) is attached to this Amendment as Exhibit G and such Exhibit G is hereby added as a new exhibit to the UAA (“NMX-PUD Document”).
Modifications and updates. ATL may automatically update the Licensed Software, from time to time in its sole discretion, including any of the services, software or databases contained therein, with any updates prepared for commercial release. Licensee hereby authorizes ATL to update, maintain, and modify the Licensed Software. Without limiting the generality of the foregoing, ATL may, from time to time, establish or change various practices, limitations, and restrictions for administering such Licensed Software.
Modifications and updates. Circle reserves the right, in its sole discretion, to modify or
Modifications and updates. 10.1 The LICENSOR can create and develop updates of the software at any time. The LICENSEE thus has no right to request a modification or an update.
10.2 When an update has been purchased, all usage-rights of the old software expire. The "Single", "Runtime" and "Enterprise"- licenses also include updates of the software up to the but excluding the next major release of the software. The software-versions are labeled in the usual format "[major].[minor].[build]". An example should illustrate this: When the LICENSEE purchases the software in the version "1.2.10", the LICENSEE is also allowed to update to the version "1.
9.2 without purchasing a new license. The LICENSEE needs to purchase a new license in the above example from version "2.0.0" onwards.