From a84e277835c43582b49584cb3eb5d50488336bc0 Mon Sep 17 00:00:00 2001 From: Thienky Dang Date: Thu, 4 Jun 2026 10:31:19 -0500 Subject: [PATCH] Fix amendment typo in README (#46820) **Related issue:** Resolves # # Checklist for submitter If some of the following don't apply, delete the relevant line. - [ ] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. See [Changes files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/guides/committing-changes.md#changes-files) for more information. - [ ] Input data is properly validated, `SELECT *` is avoided, SQL injection is prevented (using placeholders for values in statements), JS inline code is prevented especially for url redirects, and untrusted data interpolated into shell scripts/commands is validated against shell metacharacters. - [ ] Timeouts are implemented and retries are limited to avoid infinite loops - [ ] If paths of existing endpoints are modified without backwards compatibility, checked the frontend/CLI for any necessary changes ## Testing - [ ] Added/updated automated tests - [ ] Where appropriate, [automated tests simulate multiple hosts and test for host isolation](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/reference/patterns-backend.md#unit-testing) (updates to one hosts's records do not affect another) - [ ] QA'd all new/changed functionality manually For unreleased bug fixes in a release candidate, one of: - [ ] Confirmed that the fix is not expected to adversely impact load test results - [ ] Alerted the release DRI if additional load testing is needed ## Database migrations - [ ] Checked schema for all modified table for columns that will auto-update timestamps during migration. - [ ] Confirmed that updating the timestamps is acceptable, and will not cause unwanted side effects. - [ ] Ensured the correct collation is explicitly set for character columns (`COLLATE utf8mb4_unicode_ci`). ## New Fleet configuration settings - [ ] Setting(s) is/are explicitly excluded from GitOps If you didn't check the box above, follow this checklist for GitOps-enabled settings: - [ ] Verified that the setting is exported via `fleetctl generate-gitops` - [ ] Verified the setting is documented in a separate PR to [the GitOps documentation](https://github.com/fleetdm/fleet/blob/main/docs/Configuration/yaml-files.md#L485) - [ ] Verified that the setting is cleared on the server if it is not supplied in a YAML file (or that it is documented as being optional) - [ ] Verified that any relevant UI is disabled when GitOps mode is enabled ## fleetd/orbit/Fleet Desktop - [ ] Verified compatibility with the latest released version of Fleet (see [Must rule](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/workflows/fleetd-development-and-release-strategy.md)) - [ ] If the change applies to only one platform, confirmed that `runtime.GOOS` is used as needed to isolate changes - [ ] Verified that fleetd runs on macOS, Linux and Windows - [ ] Verified auto-update works from the released version of component to the new version (see [tools/tuf/test](../tools/tuf/test/README.md)) --- handbook/people/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/handbook/people/README.md b/handbook/people/README.md index dae10d6ae3..9612d4854f 100644 --- a/handbook/people/README.md +++ b/handbook/people/README.md @@ -135,8 +135,8 @@ When People receives [notification of a Fleetie's role changing](https://fleetdm - Under the "Compensation" heading, select edit and update the "Job title" and input the specific date the change happened. Save the changes. - For updating Remote (non-US Fleeties): - Log in to Remote and navigate to "Requests". - - Click "New Request" and select the employee from the dropdown box. Then, select "Employee Agreement Amendement". - - Follow Remote's prompts to complete the amendement. + - Click "New Request" and select the employee from the dropdown box. Then, select "Employee Agreement Amendment". + - Follow Remote's prompts to complete the amendment. - Take any relevant follow-up steps as directed by Remote in order to make the required changes to the Fleetie's profile. @@ -252,7 +252,7 @@ To [change a teammate's compensation](https://fleetdm.com/handbook/company/commu 4. Once compensation decisions have been finalized, the Head of People will send the teammate's manager a Slack DM to communicate the compensation decision and asking them to inform the teammate. 5. Update the respective payroll platform (Gusto or Remote): - In Gusto, navigate to the personnel page, selecting salary field, and updating with an effective date that makes the next payroll. - - In Remote, navigate to "Requests", start a new request, select the employee from the dropdown box, and begin the process for an employee agreement amendement. + - In Remote, navigate to "Requests", start a new request, select the employee from the dropdown box, and begin the process for an employee agreement amendment. 7. Update the [equity spreadsheet](https://docs.google.com/spreadsheets/d/1_GJlqnWWIQBiZFOoyl9YbTr72bg5qdSSp4O3kuKm1Jc/edit?usp=sharing) (internal doc) by adding to the "Notes" cell. - Update the "ΒΆΒΆ Annual OTE ($)" column with the new compensation information. - Update the "Last compensation change" column with the effective date from payroll platform.