[libadwaita/wip/exalm/value-objects: 2/4] doc: Mention `AdwValueObject` removal in the migration guide

[Alexander Mikhaylenko <alexm src gnome org>]

commit badbfb36bf35aa933e14c7f7de1b497b33ad199c
Author: Alexander Mikhaylenko <alexm gnome org>
Date:   Tue Jun 1 14:15:40 2021 +0500

    doc: Mention `AdwValueObject` removal in the migration guide

 doc/migrating-libhandy-1-4-to-libadwaita.md | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)
---
diff --git a/doc/migrating-libhandy-1-4-to-libadwaita.md b/doc/migrating-libhandy-1-4-to-libadwaita.md
index 0d3e58de..891f5a42 100644
--- a/doc/migrating-libhandy-1-4-to-libadwaita.md
+++ b/doc/migrating-libhandy-1-4-to-libadwaita.md
@@ -77,7 +77,12 @@ used for managing children instead of `GtkContainer` API. In Libadwaita
 [property Adw Flap:separator] are the only way to manage [class Adw Flap]
 children.
 
-Adding children in a UI file still works.
+### Stop Using `HdyValueObject` with non-string values
+
+`HdyValueObject` has been removed. While it's not practical to replace the cases
+where it's storing strings in GTK3, as the preferred replacement only exists in
+4, it can also be used with any other `GValue`. That use has no replacement and
+you can instead create your own objects to store those values.
 
 ## Changes that Need to Be Done at the Time of the Switch
 
@@ -165,6 +170,11 @@ The `HdyComboRow:selected-index` property has been renamed to
 [class@Adw.EnumValueObject] can no longer be manually created and is only
 intended to be used with [class@Adw.EnumListModel].
 
+### Stop Using `HdyValueObject`
+
+`HdyValueObject` has been removed. The typical use for storing strings in
+combination with `GListStore` can be replaced by using [class@Gtk.StringList].
+
 ### Adapt to [class@Adw.HeaderBar] API Changes
 
 [class@Adw.HeaderBar] API mostly mirrors [class@Gtk.HeaderBar], refer to the