docs: Note that schema can be a Schema

Author: eemeli

docs/03_options.md

@@ -72,15 +72,15 @@ The `!!value` and `!!yaml` types are not supported.
 
 Used by: `parse()`, `parseDocument()`, `parseAllDocuments()`, `stringify()`, `new Composer()`, `new Document()`, and `doc.setSchema()`
 
-| Name             | Type                                 | Default                                   | Description                                                                                                                                                                                                        |
-| ---------------- | ------------------------------------ | ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| compat           | `string ⎮ Tag[] ⎮ null`              | `null`                                    | When parsing, warn about compatibility issues with the given schema. When stringifying, use scalar styles that are parsed correctly by the `compat` schema as well as the actual schema.                           |
-| customTags       | `Tag[] ⎮ function`                   |                                           | Array of [additional tags](#custom-data-types) to include in the schema                                                                                                                                            |
-| merge            | `boolean`                            | 1.1:&nbsp;`true` 1.2:&nbsp;`false`        | Enable support for `<<` merge keys. Default value depends on YAML version.                                                                                                                                         |
-| resolveKnownTags | `boolean`                            | `true`                                    | When using the `'core'` schema, support parsing values with these explicit [YAML 1.1 tags]: `!!binary`, `!!omap`, `!!pairs`, `!!set`, `!!timestamp`. By default `true`.                                            |
-| schema           | `string`                             | 1.1:&nbsp;`'yaml-1.1'` 1.2:&nbsp;`'core'` | The base schema to use. Default value depends on YAML version. Built-in support is provided for `'core'`, `'failsafe'`, `'json'`, and `'yaml-1.1'`. If using another value, `customTags` must be an array of tags. |
-| sortMapEntries   | `boolean ⎮` `(a, b: Pair) => number` | `false`                                   | When stringifying, sort map entries. If `true`, sort by comparing key values using the native less-than `<` operator.                                                                                              |
-| toStringDefaults | `ToStringOptions`                    |                                           | Override default values for `toString()` options.                                                                                                                                                                  |
+| Name             | Type                                 | Default                                   | Description                                                                                                                                                                                                               |
+| ---------------- | ------------------------------------ | ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| compat           | `string ⎮ Tag[] ⎮ null`              | `null`                                    | When parsing, warn about compatibility issues with the given schema. When stringifying, use scalar styles that are parsed correctly by the `compat` schema as well as the actual schema.                                  |
+| customTags       | `Tag[] ⎮ function`                   |                                           | Array of [additional tags](#custom-data-types) to include in the schema                                                                                                                                                   |
+| merge            | `boolean`                            | 1.1:&nbsp;`true` 1.2:&nbsp;`false`        | Enable support for `<<` merge keys. Default value depends on YAML version.                                                                                                                                                |
+| resolveKnownTags | `boolean`                            | `true`                                    | When using the `'core'` schema, support parsing values with these explicit [YAML 1.1 tags]: `!!binary`, `!!omap`, `!!pairs`, `!!set`, `!!timestamp`. By default `true`.                                                   |
+| schema           | `string ⎮ Schema`                    | 1.1:&nbsp;`'yaml-1.1'` 1.2:&nbsp;`'core'` | The base schema to use. Default value depends on YAML version. Built-in support is provided for `'core'`, `'failsafe'`, `'json'`, and `'yaml-1.1'`. If using another string value, `customTags` must be an array of tags. |
+| sortMapEntries   | `boolean ⎮` `(a, b: Pair) => number` | `false`                                   | When stringifying, sort map entries. If `true`, sort by comparing key values using the native less-than `<` operator.                                                                                                     |
+| toStringDefaults | `ToStringOptions`                    |                                           | Override default values for `toString()` options.                                                                                                                                                                         |
 
 [yaml 1.1 tags]: https://yaml.org/type/