fixup: flags changed

Signed-off-by: Todd Baert <[email protected]>

docs/reference/specifications/providers.md

@@ -207,6 +207,11 @@ Conflicting properties in the context will be overwritten by the values below.
 | `$flagd.flagKey`   | the identifier for the flag being evaluated             |
 | `$flagd.timestamp` | a unix timestamp (in seconds) of the time of evaluation |
 
+### Changed Flags
+
+When a new flag definition is parsed, the stored flags are compared with the newly parsed flags.
+Flags which have been removed, added, or mutated (including their default variant, targeting rules, or metadata) have their keys added to the `flags changed` field of the associated `PROVIDER_CONFIGURATION_CHANGED` event.`
+
 ### Sync-Metadata Properties in the Evaluation Context
 
 In-process flagd providers also inject any properties returned by the [sync-metadata RPC response](./protos.md#getmetadataresponse) into the context.
@@ -223,6 +228,7 @@ The provider metadata includes the top-level metadata properties in the [flag de
 
 The in-process resolver mode can also use a file based [flag definition](../flag-definitions.md).
 This does not connect to a flagd instance or gRPC sync implementation, and instead polls a flag definition from a file.
+If the file has been modified (based on the file metadata) since the last poll, a change event with the [calculated changed flags](#changed-flags) field is emitted.  
 
 !!! note