From 231302fcfdc827a8a2b5cfba9a6980a285d7e3c2 Mon Sep 17 00:00:00 2001 From: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com> Date: Fri, 30 Jan 2026 11:25:30 +0900 Subject: [PATCH] Website typo fixes and text changes (#39034) Fixed typos and made text changes to the following pages: - Fleet GitOps - GitOps workshop - Case studies template --------- Co-authored-by: Eric --- website/views/pages/articles/case-study.ejs | 6 +--- website/views/pages/fleet-gitops.ejs | 28 +++++++++---------- .../pages/landing-pages/gitops-workshop.ejs | 12 ++++---- 3 files changed, 21 insertions(+), 25 deletions(-) diff --git a/website/views/pages/articles/case-study.ejs b/website/views/pages/articles/case-study.ejs index e7a3c182ef..fea6d4336e 100644 --- a/website/views/pages/articles/case-study.ejs +++ b/website/views/pages/articles/case-study.ejs @@ -110,11 +110,7 @@

About Fleet

-

Fleet is an Open Device Management platform. Manage configuration, application deployment, and patching from a single console. Fleet supports multiple operating systems, including macOS, iOS, Android, Windows, Linux, ChromeOS, and AWS, as well as Google Cloud, Azure Data Centers, and containers.

- -

For security and IT teams, Fleet delivers interoperability and easy automation through open standards, flexible deployment, transparent controls, and real-time visibility of your inventory.

- -

For end users, Fleet builds trust through data transparency and clarity. Devices remain reliable and well-managed, minimizing disruptions and ensuring maximum productivity.

+

Fleet is the open-source endpoint management platform that gives you total control, unlike the proprietary 'black boxes' of legacy vendors. Our open device management provides full visibility into our code and roadmap, plus a true choice of deployment—on-prem or cloud—with 100% feature parity. Our API-first approach empowers technical teams to automate with GitOps, scale confidently, and get the real-time data needed to secure their entire macOS, iOS, Windows, and Linux fleets.

Get a demo diff --git a/website/views/pages/fleet-gitops.ejs b/website/views/pages/fleet-gitops.ejs index dd1d04c4f2..0bed7869e0 100644 --- a/website/views/pages/fleet-gitops.ejs +++ b/website/views/pages/fleet-gitops.ejs @@ -16,7 +16,7 @@
Get to know Fleet GitOps
-

Implement collaboration, version control, and automation workflows built into Fleet that accelerate OS updates, software deployments and reduce downtime.

+

Implement collaboration, version control, and automation workflows built into Fleet that accelerates enforcing controls, OS updates, software deployments, and reduce downtime.

Learn more
@@ -48,16 +48,16 @@
- An image showing the process of the Fleet Gitops workflow. A developer pushes a device management profile to GitHub, An IT admin approves the new profile. When the updated profile is merged the CI/CD runner sends the profile to a Fleet server. The Fleet server then sends the updated profile to a managed device and verifies the result. + An image showing the process of the Fleet Gitops workflow. A developer pushes a device management profile to GitHub, and an IT admin approves the new profile. When the updated profile is merged, the CI/CD runner sends the profile to a Fleet server. The Fleet server then sends the updated profile to a managed device and verifies the result.
-

Fleet GitOps commands to modify the Fleet UI are executed by the fleetctl binary (the “engine” under the hood.) The binary lives on a CI / CD “runner” (e.g., GitHub Actions.) A git push with updated YAML code kicks off automation that >results in real-time changes you can see.

+

Fleet GitOps commands to modify the Fleet UI are executed by the fleetctl binary (the “engine” under the hood.) The binary lives on a CI / CD “runner” (e.g., GitHub Actions). A git push with updated YAML code kicks off automation that results in real-time changes you can see.

Declarative device management

Most device management solutions have an API, but most do not provide comprehensive control over the admin console with configuration-as-code like Fleet.

Managing the Fleet UI console with GitOps means you have total declarative control over your devices.

-

Using GitOps with Fleet unlocks powerful automations that allow you to:

+

Unlock powerful automations that allow you to:

  • Ensure every change is peer-reviewed
  • Ensure every setting is version-controlled
    • @@ -68,9 +68,9 @@
    Observable, reversible, and repeatable workflows
    -

    Nothing builds knowledge, trust and fosters engineering teamwork like peer-reviewed changes made in the open.

    -

    Collaboration on Fleet GitOps workflows helps to prevent problems before they occur. Version control means it is straight-forward to fix problems that do make it into production (nobody’s perfect...)

    -

    Another powerful technical benefit: less effort on long-term maintenance. Controlling the Fleet UI with code effectively means creating a library of stable, known-good configurations. They can be copied and modified for easily adding new management objects like device profiles and software installations without the endless sprawl of manually re-creating automations and scoping.

    +

    Nothing builds knowledge, trust, and fosters engineering teamwork like peer-reviewed changes made in the open.

    +

    Collaboration on Fleet GitOps workflows helps to prevent problems before they occur. Version control means it is straightforward to fix problems that do make it into production (nobody’s perfect...)

    +

    Another powerful technical benefit: less effort on long-term maintenance. Controlling the Fleet UI with code results in a library of stable, known-good configurations that can be copied and modified to easily add new management objects, like device profiles and software. Tame the endless sprawl of manually re-creating automations and scoping.

@@ -86,11 +86,11 @@
Stay the course
-

Changes made in the console or to devices directly can cause device state to “drift” - away from compliance, security posture and an organization’s intended user experience.

+

Changes made in the console or to devices directly can cause device state to “drift” - away from compliance, security posture, and an organization’s intended user experience.

Choose automation over repetition
-

Applications build muscle memory. But, what could you do with the time gained back from manual tasks and visual scans in your current device management solution?

+

Applications build muscle memory. But what could you do with the time gained back from manual tasks and visual scans in your current device management solution?

Cancel the CAB
@@ -107,7 +107,7 @@
-

“One Fortune 500 company had a 1.5 hour Change Advisory Board (CAB) meeting, 100 attendees, and they reviewed around 50 changes per meeting. This cost them $750k not including opportunity costs.”

+

“One Fortune 500 company had a 1.5-hour Change Advisory Board (CAB) meeting, 100 attendees, and they reviewed around 50 changes per meeting. This cost them $750k not including opportunity costs.”

@@ -126,13 +126,13 @@

If DevOps or GitOps is already used by an organization, device management engineers may be aware of the concepts and tooling. Having an internal example to follow can result in an easier path to adoption.

But, GitOps adoption is not always simple. Admins may resist unfamiliar workflows or solutions. They may also have concerns about losing the value of certifications or specialized training.

-

By meeting potential challenges with phased implementation and thought leadership, any team can successfully adopt Fleet GitOps. We’ve seen it and we’ve helped our customers do it.

+

By meeting potential challenges with phased implementation and thought leadership, any team can successfully adopt Fleet GitOps. We’ve seen it, and we’ve helped our customers do it.

Making GitOps benefits real

At Fleet, we believe that showing organizations how to migrate to GitOps workflows represents an enormous opportunity for them to increase engineering efficiency and operational speed. This ultimately improves both end user experience and enterprise compliance. We design the product around these goals. We want to help you achieve them.

-

One way we can help is by improving the product itself, which we’re doing everyday.

-

Another way we can help is through training. To learn more about GitOps, you can attend one of our free, hands-on, in-person GitOps workshops, or, you can request that one be delivered in your area.

+

One way we can help is by improving the product itself, which we’re doing every day.

+

Another way we can help is through training. To learn more about GitOps, you can attend one of our free, hands-on, in-person GitOps workshops, or you can request that one be delivered in your area.

@@ -140,7 +140,7 @@
-

“The shift to GitOps has modernized our operations giving us the agility and change control we needed giving leadership real-time confidence in device health and compliance.”

+

“The shift to GitOps has modernized our operations, giving us the agility and change control we needed, giving leadership real-time confidence in device health and compliance.”

Dan Jackson diff --git a/website/views/pages/landing-pages/gitops-workshop.ejs b/website/views/pages/landing-pages/gitops-workshop.ejs index bb02f90615..9e167ea298 100644 --- a/website/views/pages/landing-pages/gitops-workshop.ejs +++ b/website/views/pages/landing-pages/gitops-workshop.ejs @@ -89,21 +89,21 @@

Optimize end user experience

-

Controlling a device management console with configuration-as-code improves compliance, handles complexity, and allows you to automate and version control your work.

+

Managing devices with configuration-as-code improves compliance, handles complexity, and allows you to automate and version control your work.

What to expect

-

The Fleet GitOps Level 1 course is a 4-hour session open to technology practitioners who are new to configuration-as-code concepts. It is primarily intended for experienced client platform engineers & systems administrators currently in device management roles.

+

The Fleet GitOps Level 1 course is a 4-hour session open to technology practitioners who are new to configuration-as-code concepts. It is primarily intended for experienced client platform engineers & systems administrators who have been in or are currently in device management roles.

What you'll need

  • Familiarity with code editing and command line tools
    • -
  • A basic understanding of git repository management
    • +
  • Knowledge of git repository management tools
  • A GitHub.com account
  • A laptop with a modern code editor and web browser
  • The GitHub Desktop app
    • @@ -130,15 +130,15 @@

    Marketable skills

    -

    Top tech companies use GitOps for managing infrastructure, CI/CD pipelines and more. Understand how to use these techniques for device management.

    +

    Top tech companies use GitOps for managing infrastructure, CI/CD pipelines, and more. Understand how to use these techniques for device management.

    A solid foundation

    -

    Device management is often difficult to audit and undo. Learn how to make your work observable and reversible. Use automations to repeat success and reduce maintenance.

    +

    Legacy management solutions can be tricky to audit and revert to a known-good state. Learn how to make your work observable, reversible, and repeatable.

    A better way

    -

    Fleet is purpose-built for GitOps. Learn how to manage Fleet through configuration-as-code and the principles of GitOps.

    +

    Fleet is API-first and GitOps-native. Understand how Fleet is different from its competitors and learn how to use Fleet and GitOps for modern device management.