From d2f56a66d8ffef94ffb482c24e35793715ae3d36 Mon Sep 17 00:00:00 2001 From: N Balachandran Date: Thu, 27 Jun 2024 12:52:09 +0530 Subject: [PATCH] doc/dev: Fix typos in encoding.rst Signed-off-by: N Balachandran (cherry picked from commit 9f43c67a639958a13fef198ffe62cf5241f1f53c) --- doc/dev/encoding.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/dev/encoding.rst b/doc/dev/encoding.rst index f065d64bd1a90..4b7598ebea09e 100644 --- a/doc/dev/encoding.rst +++ b/doc/dev/encoding.rst @@ -31,7 +31,7 @@ by a programmer by implementing the ``encode`` and ``decode`` methods. Principles for format change ---------------------------- It is not unusual that the format of serialization changes. This -process requires careful attention from during both development +process requires careful attention during both development and review. The general rule is that a decoder must understand what had been @@ -55,7 +55,7 @@ of interoperability between dencoders: * ``n-2`` for dencoding between daemons, * ``n-3`` hard requirement for client-involved scenarios, -* ``n-3..`` soft requirements for clinet-involved scenarios. Ideally +* ``n-3..`` soft requirements for client-involved scenarios. Ideally every client should be able to talk any version of daemons. As the underlying reasons are the same, the rules dencoders @@ -163,7 +163,7 @@ macro. The append-extendability of our dencoders is a result of the forward compatibility that the ``ENCODE_START`` and ``DECODE_FINISH`` macros bring. -They are implementing extendibility facilities. An encoder, when filling +They are implementing extensibility facilities. An encoder, when filling the bufferlist, prepends three fields: version of the current format, minimal version of a decoder compatible with it and the total size of all encoded fields. -- 2.39.5