docs(openexr): update ACES container mode to reflect changes to relaxed mode

Signed-off-by: glowies <[email protected]>

Author: Glowies

src/doc/builtinplugins.rst

@@ -1648,13 +1648,14 @@ control aspects of the writing itself:
      - One of `none` (default), `strict`, or `relaxed`.
        If not `none`, the spec will be checked to see if it is compliant
        with the ACES Container format defined in `ST 2065-4`_. If it is,
-       `chromaticities` will be set to the ACES AP0 ones, and the
-       `acesImageContainerFlag` attribute will be set to 1.
+       `chromaticities` will be set to the ACES AP0 ones, `colorInteropId`
+       will be set to 'lin_ap0_scene' and the `acesImageContainerFlag`
+       attribute will be set to 1.
        In `strict` mode, if the spec is non-compliant, the output will
        throw an error and avoid writing the image.
-       While in `relaxed` mode, if the spec in non-compliant, only a
-       warning will be printed and the attributes mentioned above will
-       *not* be written to the spec.
+       While in `relaxed` mode, if the spec is non-compliant, `chromaticities`
+       and `colorInteropId` will be set, but `acesImageContainerFlag`
+       will NOT.
    * - ``oiio:RawColor``
      - int
      - If nonzero, writing images with non-RGB color models (such as YCbCr)