[libsoup/carlosgc/docs-migrating-thread-safety] docs: fix section about thread safety in migration guide

[Carlos Garcia Campos <carlosgc src gnome org>]

commit 2253f0917bff36248258e607864c25db235a80ff
Author: Carlos Garcia Campos <cgarcia igalia com>
Date:   Mon Jun 20 10:59:18 2022 +0200

    docs: fix section about thread safety in migration guide
    
    Fixes #284

 docs/reference/migrating-from-libsoup-2.md | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)
---
diff --git a/docs/reference/migrating-from-libsoup-2.md b/docs/reference/migrating-from-libsoup-2.md
index 0c399aa5..9f196f39 100644
--- a/docs/reference/migrating-from-libsoup-2.md
+++ b/docs/reference/migrating-from-libsoup-2.md
@@ -156,7 +156,8 @@ buffer.
 In libsoup 2 there was an attempt at making various APIs of the library
 thread-safe. However this was never well tested, maintained, or documented.
 
-In libsoup 3 it now behaves in line with other GObject libraries. Once you
+
+libsoup 3 was initially designed to behave in line with other GObject libraries. Once you
 create a [class@Session] all usage of that session must happen on the same
-thread. You may create separate sessions per thread but in most use-cases you
-should be using the async APIs which handle non-blocking IO for you.
+thread. However, in version 3.2 thread safety support was introduced
+again, with the same approach as libsoup2.