update sip-2034 (#1723)

content/sips/sip-2034.md

@@ -39,13 +39,13 @@ The existing pDAO will be officially deprecated, and its responsibilities transf
 
 <!-- The technical specification should describe the syntax and semantics of any new feature. -->
 
-The Risk Council will consist of 3 members, elected by SNX token holders. The voting method will utilize unweighted debt shares, as is currently used for Treasury Council elections.
+The Risk Council will consist of a configurable number of members (via SCCP), elected by SNX token holders. The voting method will utilize unweighted debt shares, as is currently used for Treasury Council elections.
 
 ### Deployment Process
 
 <!-- The technical specification should describe the syntax and semantics of any new feature. -->
 
-Once implemented, all deployments must be signed and executed by the majority of both the Risk Council and the Spartan Council. This closely replicates the status quo, where the pDAO's role in governance is to validate, stage, and execute upgrades on behalf of the Spartan Council. In the proposed system, the role of the Risk Council will be to validate that the proposed change is reflected in the staged transaction. Their role is NOT to interfere in governance, but instead to ensure all protocol upgrades are validated prior to being executed.
+Once implemented, all deployments must be signed and executed by the majority of both the Risk Council and the Spartan Council. The Spartan Council will have the capability to unilaterally call new elections for the Risk Council without requiring sign off from the Risk Council. Previously, the pDAO's role in governance was to validate, stage, and execute upgrades on behalf of the Spartan Council. In the proposed system, the role of the Risk Council will be to validate that the proposed change is reflected in the staged transaction. Their role is NOT to interfere in governance, but instead to ensure all protocol upgrades are validated prior to being executed.
 
 ## Rationale