cat anomaly detectors specification (#1303) (#1324)

Co-authored-by: Tomas Della Vedova <[email protected]>

Author: lcawl

docs/style-guide.md

@@ -56,13 +56,13 @@ represented in the specification.
 ## Where to store files
 
 The content of [`/specification`](../specification) follows the rest-api-spec structure.
-Every folder represents the namespace, while every subfolder represente the API name.
+Every folder represents the namespace, while every subfolder represent the API name.
 For top level APIs, you must use the `_global` namespace.
 
 ## Using unions
 
-Using unions direclty in definitions is considereded code smell, it's recommended to create
-a type alias that describes the union. These alises do not need to live in common files
+Using unions directly in definitions is considered code smell, it's recommended to create
+a type alias that describes the union. These aliases do not need to live in common files
 unless those are truly commonly used throughout the specification.
 
 ```ts
@@ -81,7 +81,7 @@ type Id = string | number
 ## Arrays
 
 It's fine to use the short TypeScript array notation, unless the type
-becomes more comples (eg: array of unions), in such case prefer the full definition.
+becomes more complex (eg: array of unions), in such case prefer the full definition.
 
 ```ts
 class Foo {