Glossary

The glossary is not part of the documentation. It lives under resources, at Glossary, and is defined once there — because the same terms appear in the articles, in the guides and here.

What it holds

The vocabulary of the job, not of the product: maintenance window, CVE, CVSS, KEV, change freeze, BIA, RTO/RPO, end of support, blast radius. Each entry carries the definition, the expansion where there is an acronym, the other names the same thing goes by, and links to neighboring terms.

Entries are grouped into five categories: scheduling and coordination · vulnerabilities and patches · risk and impact · regulation and audit · infrastructure.

The difference between the glossary and the documentation

The glossary defines a term as the industry uses it. The documentation describes what the product does with it.

"Collision" in the glossary is two overlapping windows on dependent systems, and why each of them is perfectly valid on its own. In the documentation, the same word is a check that runs while the date is being chosen and raises a warning. Same term, two different questions — so two places.

Searching across the languages

The glossary's search box also scans each entry's alternative names, so an English search finds the Hebrew entry and the other way round. A term that exists in only one language still appears in the list in both, with a badge saying which language it is written in, rather than disappearing.