docs: Fix typos (#1141)

substrate/srml/council/src/seats.rs

@@ -51,7 +51,7 @@ use system::{self, ensure_signed};
 // to keep the system as stateless as possible (making it a bit easier to reason about), we just
 // restrict when votes can begin to blocks that lie on boundaries (`voting_period`).
 
-// for an approval vote of C councilers:
+// for an approval vote of C councillors:
 
 // top K runners-up are maintained between votes. all others are discarded.
 // - candidate removed & bond returned when elected.
@@ -63,7 +63,7 @@ use system::{self, ensure_signed};
 // they fall in the top K+C voted can present themselves. they get the total stake
 // recorded (based on the snapshot); an ordered list is maintained (the leaderboard). Noone may
 // present themselves that, if elected, would result in being included twice on the council
-// (important since existing councilers will will have their approval votes as it may be that they
+// (important since existing councillors will have their approval votes as it may be that they
 // don't get removed), nor if existing presenters would mean they're not in the top K+C.
 
 // following B blocks, the top C candidates are elected and have their bond returned. the top C
@@ -72,7 +72,7 @@ use system::{self, ensure_signed};
 // vote-clearing happens lazily; for an approval to count, the most recent vote at the time of the
 // voter's most recent vote must be no later than the most recent vote at the time that the
 // candidate in the approval position was registered there. as candidates are removed from the
-// register and others join in their place, this prevent an approval meant for an earlier candidate
+// register and others join in their place, this prevents an approval meant for an earlier candidate
 // being used to elect a new candidate.
 
 // the candidate list increases as needed, but the contents (though not really the capacity) reduce