Move 'exception safety' section closer to the related exception guarantees section in Decoder/Encoder docs.

Author: sandwwraith

core/commonMain/src/kotlinx/serialization/encoding/Decoding.kt

@@ -52,11 +52,17 @@ import kotlinx.serialization.modules.*
  * (`{` or `[`, depending on the descriptor kind), returning the [CompositeDecoder] that is aware of colon separator,
  * that should be read after each key-value pair, whilst [CompositeDecoder.endStructure] will parse a closing bracket.
  *
- * ### Exception guarantees.
- * For the regular exceptions, such as invalid input, missing control symbols or attributes and unknown symbols,
+ * ### Exception guarantees
+ *
+ * For the regular exceptions, such as invalid input, missing control symbols or attributes, and unknown symbols,
  * [SerializationException] can be thrown by any decoder methods. It is recommended to declare a format-specific
  * subclass of [SerializationException] and throw it.
  *
+ * ### Exception safety
+ *
+ * In general, catching [SerializationException] from any of `decode*` methods is not allowed and produces unspecified behavior.
+ * After thrown exception, the current decoder is left in an arbitrary state, no longer suitable for further decoding.
+ *
  * ### Format encapsulation
  *
  * For example, for the following deserializer:
@@ -79,11 +85,6 @@ import kotlinx.serialization.modules.*
  * }
  * ```
  *
- * ### Exception safety
- *
- * In general, catching [SerializationException] from any of `decode*` methods is not allowed and produces unspecified behaviour.
- * After thrown exception, current decoder is left in an arbitrary state, no longer suitable for further decoding.
- *
  * This deserializer does not know anything about the underlying data and will work with any properly-implemented decoder.
  * JSON, for example, parses an opening bracket `{` during the `beginStructure` call, checks that the next key
  * after this bracket is `stringValue` (using the descriptor), returns the value after the colon as string value

core/commonMain/src/kotlinx/serialization/encoding/Encoding.kt

@@ -51,11 +51,17 @@ import kotlinx.serialization.modules.*
  * (`{` or `[`, depending on the descriptor kind), returning the [CompositeEncoder] that is aware of colon separator,
  * that should be appended between each key-value pair, whilst [CompositeEncoder.endStructure] will write a closing bracket.
  *
- * ### Exception guarantees.
+ * ### Exception guarantees
+ *
  * For the regular exceptions, such as invalid input, conflicting serial names,
  * [SerializationException] can be thrown by any encoder methods.
  * It is recommended to declare a format-specific subclass of [SerializationException] and throw it.
  *
+ * ### Exception safety
+ *
+ * In general, catching [SerializationException] from any of `encode*` methods is not allowed and produces unspecified behaviour.
+ * After thrown exception, the current encoder is left in an arbitrary state, no longer suitable for further encoding.
+ *
  * ### Format encapsulation
  *
  * For example, for the following serializer:
@@ -83,11 +89,6 @@ import kotlinx.serialization.modules.*
  * machinery could be completely different.
  * In any case, all these parsing details are encapsulated by an encoder.
  *
- * ### Exception safety
- *
- * In general, catching [SerializationException] from any of `encode*` methods is not allowed and produces unspecified behaviour.
- * After thrown exception, current encoder is left in an arbitrary state, no longer suitable for further encoding.
- *
  * ### Encoder implementation.
  *
  * While being strictly typed, an underlying format can transform actual types in the way it wants.