Update sip-353.md (#1885)

add multisig setup, and more clarity to the tenure

content/sips/sip-353.md

@@ -72,10 +72,10 @@ Formalizing the support role acknowledges the complexities of decentralized gove
 **Protocol Roadmap:** The CL is responsible for maintaining the roadmap determined by the SC in a public place, to be updated in the first month and reported against in the final month of each epoch.
 
 **CC Funding:**
-Each governance epoch, the CL prepares a structured funding schedule and criteria for budget, to be reviewed and approved by the Treasury Council.
+Each governance epoch, the CL prepares a structured funding schedule and criteria for budget, to be reviewed and approved by the Treasury Council. CC funds are to be held in a 2/3 multisig, with the CL, the CC Support Role, and the TC Multsig as signers.
 
 **CL Appointment:**
-On passing of this proposal, and then at the end of September and March, voting for the CL will take place via snapshot or similar tool. Any current CCs can nominate, and one CL is elected by the SC in a single appointment. 
+On passing of this proposal, and then at the end of September and March, voting for the CL will take place via snapshot or similar tool. As a result, the expected tenure of CL epochs is 6 months. Any current CCs can nominate themselves in the second last week of the term, and one CL is elected by the SC in a single appointment, in the final week of the term.
 
 **CC Support:**
 The existing operational role with the CCs will become part of governance operations, and takes part in implementing the decisions of the SC, TC and CL. 
@@ -91,4 +91,4 @@ N/A
 N/A
 
 ## Copyright
-Copyright and related rights waived via CC0.
+Copyright and related rights waived via CC0.