From 76d24d5f165498b5743c72932b82b5824744f640 Mon Sep 17 00:00:00 2001
From: Sergey Fursov <geyser85@gmail.com>
Date: Mon, 27 Dec 2021 14:51:43 +0300
Subject: [PATCH] [4.0.x] Updated example of YAML serialization format in docs.

Backport of feeb0685c62a793c55a058584ba1de45e74f80f7 from main
---
 docs/topics/serialization.txt | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/docs/topics/serialization.txt b/docs/topics/serialization.txt
index 586d7ff13a..ae826c15b9 100644
--- a/docs/topics/serialization.txt
+++ b/docs/topics/serialization.txt
@@ -330,9 +330,10 @@ YAML serialization looks quite similar to JSON. The object list is serialized
 as a sequence mappings with the keys "pk", "model" and "fields". Each field is
 again a mapping with the key being name of the field and the value the value::
 
-    -   fields: {expire_date: !!timestamp '2013-01-16 08:16:59.844560+00:00'}
-        model: sessions.session
-        pk: 4b678b301dfd8a4e0dad910de3ae245b
+    - model: sessions.session
+      pk: 4b678b301dfd8a4e0dad910de3ae245b
+      fields:
+        expire_date: 2013-01-16 08:16:59.844560+00:00
 
 Referential fields are again represented by the PK or sequence of PKs.