From b27d60faf5368ca677b46aa28b37ed3392d59c4f Mon Sep 17 00:00:00 2001 From: Pedro Borges Date: Thu, 9 Oct 2025 13:18:11 -0300 Subject: [PATCH] Fix spelling error in "IT and Enablement" (#33988) --- handbook/it-and-enablement/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/handbook/it-and-enablement/README.md b/handbook/it-and-enablement/README.md index 007cf7de90..a78b98b77a 100644 --- a/handbook/it-and-enablement/README.md +++ b/handbook/it-and-enablement/README.md @@ -36,7 +36,7 @@ When procuring SaaS tools and services, analyze the purchase of these subscripti - Get product demos whenever possible. Does the product do what it's supposed to do in the way that it is supposed to do it? - Avoid extra features you don't need, and if they're there anyway, avoid using them. - Data portability: is it possible for Fleet to export it's data if we stop using it? Is it easy to pull that data in an understandable format? -- Programability: Does it have a publicly documented legible REST API that requires at most a single API token? +- Programmability: Does it have a publicly documented legible REST API that requires at most a single API token? - Intentionality: The product fits into other tools and processes that Fleet uses today. Avoid [unintended consequences](https://en.wikipedia.org/wiki/Midas). The tool will change to fit the company, or we won't use it.