From 2ff1d021bb006d8f8db1b3f1e703ee55bcee2187 Mon Sep 17 00:00:00 2001 From: Mikko Pesari Date: Mon, 6 May 2024 18:01:21 +0300 Subject: [PATCH] doc: fix some typos --- docs/pages/serialization/normalizer.md | 2 +- docs/pages/usage/type-strictness-and-flexibility.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/pages/serialization/normalizer.md b/docs/pages/serialization/normalizer.md index 096a69a1..b0fd6569 100644 --- a/docs/pages/serialization/normalizer.md +++ b/docs/pages/serialization/normalizer.md @@ -51,7 +51,7 @@ unsupported by serialization functions like `json_encode()`: - Objects are transformed to arrays based on their properties, no matter their visibility (public, protected or private) - Dates are formatted to the RFC 3339 format -- Baked enums use their value, unit enums use their name +- Backed enums use their value, unit enums use their name Custom transformations can be applied, see [normalizer extension chapter] for more information. diff --git a/docs/pages/usage/type-strictness-and-flexibility.md b/docs/pages/usage/type-strictness-and-flexibility.md index 1d1f5ec4..e3a10140 100644 --- a/docs/pages/usage/type-strictness-and-flexibility.md +++ b/docs/pages/usage/type-strictness-and-flexibility.md @@ -42,7 +42,7 @@ $flexibleMapper->map('int', '42'); // List type will accept non-incremental keys. $flexibleMapper->map('list', ['foo' => 42, 'bar' => 1337]); -// => [0 => 42, 1 => 1338] +// => [0 => 42, 1 => 1337] // --- // If a value is missing in a source for a node that accepts `null`, the