diff --git a/website/src/pages/specification/20241027-flagsets.md b/website/src/pages/specification/20241027-flagsets.md
index 6809ca3794c..0313b0ec677 100644
--- a/website/src/pages/specification/20241027-flagsets.md
+++ b/website/src/pages/specification/20241027-flagsets.md
@@ -14,9 +14,8 @@ Description: Flag sets are a way to group flags together.
 
 ## Definition
 
-> A collection of related flags. This grouping helps organize feature flags based on their intended use, facilitating easier management and deployment.
-
-_Source: [Openfeature glossary](https://openfeature.dev/specification/glossary/#flag-set)._
+> A collection of related flags. This grouping helps organize feature flags based on their intended use, facilitating easier management and deployment.  
+> _Source: [Openfeature glossary](https://openfeature.dev/specification/glossary/#flag-set)._
 
 
 ## Context
@@ -144,6 +143,7 @@ authorizedKeys:
 - It is easy to give ownership of a flag set to a team, by giving them access to the file.
 
 **CON**
+- The flag set configuration is at the same place as the flag configuration, so it is possible to edit the flag set name directly inside the file _(risk of overriding another flag set)_.
 - If we want the same flag to be part of multiple flag sets, we need to duplicate the flag in multiple files.
 
 ### Solution 2: specify the flag set in the retriever configuration
@@ -190,6 +190,16 @@ authorizedKeys:
   admin:
     - apikey3
 ```
+
+**PRO**
+- It is simple to configure a flag set by putting all the flags at the same place.
+- It is easy to understand which flags are part of a flag set.
+- It is easy to give ownership of a flag set to a team, by giving them access to the file.
+- The flag set name is directly associated to the retriever, so it is not possible to edit it directly inside the file.
+
+**CON**
+- If we want the same flag to be part of multiple flag sets, we need to duplicate the flag in multiple files.
+
 ### Solution 3
 :::note
 Feel free to propose other solutions here.