(#530) Update terms of service

[steviecoaster]

Description Of Changes

Updated Terms with the following:

- Use the Site and associated services for purposes of managing organizational machines. Organizations using Chocolatey should be using different repositories, such as their own internal repositories. Exceptions to this include:
  - the use of package repository solutions that use the community repository as an "upstream" to cache packages locally on that repository server.
  - Managing your personal work computer(s)

In addition, ensured LastUpdated was set to 21 May, 2026

Motivation and Context

We need the updated terms to be on the website

Testing

Operating Systems Testing

Change Types Made

• Bug fix (non-breaking change).
• Feature / Enhancement (non-breaking change).
• Breaking change (fix or feature that could cause existing functionality to change).
• Documentation changes.
• PowerShell code changes.

Change Checklist

• Requires a change to the documentation.
• Documentation has been updated.
• Tests to cover my changes, have been added.
• All new and existing tests passed?
• PowerShell code changes: PowerShell v3 compatibility checked?
• All items are complete on the Definition of Done.

Related Issue

Fixes #530

[st3phhays]

@pauby Would you be able to give this a final lookover? I can look to get it merged after.

The failing GitHub Workflow Action for the yarn npm audit will be addressed in a separate PR, so I am ok with bypassing this here.

This will go out with choco-theme 2.9.0.

[pauby]

It's the same typo in most of them.

I also stopped adding a comment for the dates to be updated, but if we're updating one we need to update them all of course.

[st3phhays]

It's the same typo in most of them.

I also stopped adding a comment for the dates to be updated, but if we're updating one we need to update them all of course.

@pauby For future reviews, anything located in the /dist folder does not need to be reviewed 1 by 1, since those are artifacts that are automatically generated from running yarn build. It is important though to ensure that those artifacts are generated after all review comments have been addressed. These are the files that end up in the different packages we publish.

[st3phhays]

@ferventcoder This is the newly added content to the Terms.

[ferventcoder]

This is what does not take effect until January 1, 2027.