diff --git a/product_docs/docs/pgd/5/sequences.mdx b/product_docs/docs/pgd/5/sequences.mdx
index 78e9dfd457d..af7f246af30 100644
--- a/product_docs/docs/pgd/5/sequences.mdx
+++ b/product_docs/docs/pgd/5/sequences.mdx
@@ -52,7 +52,8 @@ There are various possible algorithms for global sequences:
 SnowflakeId sequences generate values using an algorithm that doesn't require
 inter-node communication at any point. It's faster and more robust and has the 
 useful property of recording the timestamp when the values were
-created.
+created. Snowflake sequences are generally the preferred sequence option if the
+application can support it.
 
 SnowflakeId sequences have the restriction that they work only for 64-bit BIGINT
 datatypes and produce values up to 19 digits long. This might be too long for
@@ -229,6 +230,10 @@ support renaming `galloc` sequences or moving them to another namespace or
 renaming the namespace that contains a `galloc` sequence. Be
 mindful of this limitation while designing application schema.
 
+Additionally, after restoring a node from a backup, all galloc sequences must manually have 
+their next value set to the maximum value of the related column. 
+See ["Set a new start value for the sequence"](#2-set-a-new-start-value-for-the-sequence).
+
 #### Converting a local sequence to a galloc sequence
 
 Before transforming a local sequence to galloc, you need to take care of several