From 9b2b79eebebb9a5c6246d8e2e44f217ec12ac95d Mon Sep 17 00:00:00 2001 From: Dale Ribeiro Date: Mon, 20 Apr 2026 17:54:22 -0400 Subject: [PATCH] Fix typo in GitOps migration documentation --- articles/migrating-to-gitops-using-fleetctl.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/articles/migrating-to-gitops-using-fleetctl.md b/articles/migrating-to-gitops-using-fleetctl.md index 88a9a8b4f1..7dba5451ab 100644 --- a/articles/migrating-to-gitops-using-fleetctl.md +++ b/articles/migrating-to-gitops-using-fleetctl.md @@ -40,7 +40,7 @@ To have `generate-gitops` output sensitive info in plaintext in your files, you The `generate-gitops` tool includes a few other options to make migrating to GitOps easier: - `--print` : Print the configuration to `stdout` rather than to files. -- `--team` : **Available in Fleet Premium.** Only output the configuration files of the fleet with the specified name. Global or "Unassgined" configuration may be output using `--team global` or `--team no-team`. +- `--team` : **Available in Fleet Premium.** Only output the configuration files of the fleet with the specified name. Global or "Unassigned" configuration may be output using `--team global` or `--team no-team`. - `--key` : Display the value of a specific, dot-delimited key, e.g. `agent_options.config.decorators`. Searches for the given key in the global configuration by default; use in conjunction with `--team` to output config from a specific fleet. See `fleetctl generate-gitops --help` for all options. @@ -56,4 +56,4 @@ See `fleetctl generate-gitops --help` for all options. - \ No newline at end of file +