diff --git a/messages/council_rules/2.txt b/messages/council_rules/2.txt
index b55034f..d8aa2e2 100644
--- a/messages/council_rules/2.txt
+++ b/messages/council_rules/2.txt
@@ -1,9 +1,9 @@
 **Emeritus**
-1. The clan chat rank for Emeritus is General :Rank_General: and unaffected against inactivity demotions.
-2. Emeritus is, who...
-2.1 founded Dakiny.
-2.2 was elected as Clan Leader and was active as Clan Leader for at least one entire quarter.
-2.3 was nominated and successfully elected in an Emeritus poll.
-2.4 donated more than 200m to the RS3 clan funds (multiple transactions will be added together).
-2.5 has recruited more than 40 members to the clan.
-2.6 served as admin for 2 years or longer.
\ No newline at end of file
+**1** The clan chat rank for Emeritus is General <:Rank_General:479008158027874315> and unaffected against inactivity demotions.
+**2** Emeritus is, who...
+**2.1** founded Dakiny.
+**2.2** was elected as Clan Leader and was active as Clan Leader for at least one entire quarter.
+**2.3** was nominated and successfully elected in an Emeritus poll.
+**2.4** donated more than 200m to the RS3 clan funds (multiple transactions will be added together).
+**2.5** has recruited more than 40 members to the clan.
+**2.6** served as admin for 2 years or longer.
\ No newline at end of file
diff --git a/messages/council_rules/3.txt b/messages/council_rules/3.txt
index 5ee628d..be738c4 100644
--- a/messages/council_rules/3.txt
+++ b/messages/council_rules/3.txt
@@ -2,7 +2,7 @@
 
 *Refer to <#667091901551345684> for how promotions / demotions are generally ruled*.
 
-**#1** Any star-related rank change (Lieutenants <:Rank_Lieutenant:479008102478512128>, Captains <:Rank_Captain:479008128893976576>, Generals <:Rank_General:479008158027874315>) **must** be voted on via a poll in <#666645356838125607>.
-**#2** "Banana" ranks (Recruit <:Rank_Recruit:479007976200601604>, Corporal <:Rank_Corporal:479008028880928768>, Sergeant <:Rank_Sergeant:479008059083980811>) are managed without specific communication, but must follow the rules listed in <#667091901551345684>.
-**#3** Possible future Daks (recruits) must have passed a guesting trial of 7 days and attended to at least 1 clan event before being invited to Dakiny.
-**#4** Any new guests, or member invitations must be posted in <#666426416337911818> so we may maintain our member spreadsheet.
+**1** Any star-related rank change (Lieutenants <:Rank_Lieutenant:479008102478512128>, Captains <:Rank_Captain:479008128893976576>, Generals <:Rank_General:479008158027874315>) **must** be voted on via a poll in <#666645356838125607>.
+**2** "Banana" ranks (Recruit <:Rank_Recruit:479007976200601604>, Corporal <:Rank_Corporal:479008028880928768>, Sergeant <:Rank_Sergeant:479008059083980811>) are managed without specific communication, but must follow the rules listed in <#667091901551345684>.
+**3** Possible future Daks (recruits) must have passed a guesting trial of 7 days and attended to at least 1 clan event before being invited to Dakiny.
+**4** Any new guests, or member invitations must be posted in <#666426416337911818> so we may maintain our member spreadsheet.
diff --git a/messages/council_rules/4.txt b/messages/council_rules/4.txt
index 3116f87..1331c4d 100644
--- a/messages/council_rules/4.txt
+++ b/messages/council_rules/4.txt
@@ -1,16 +1,16 @@
 > __**Server management rules**__
 
-**#1** Channels must not be deleted and should be archived.
-**#2** When archiving a channel, use the *Hidden categories* and archive according to the description. For example, an old event channel should be archived in *Hidden | Events archives* category.
-**#3** If a public channel hasn't been used for over a month, it can be marked with the following message and then archived. 
+**1** Channels must not be deleted and should be archived.
+**2** When archiving a channel, use the `Hidden categories` and archive according to the description. For example, an old event channel should be archived in `Hidden | Events archives` category.
+**3** If a public channel hasn't been used for over a month, it can be marked with the following message and then archived. 
 
 > ⚠️ This channel was marked for deletion ⚠️ 
 > If you want to save this channel, speak now and help keep it alive.
 > If no one says anything, this channel will be deleted in 7 days. Salvage any pictures or information you want before then.
 
-**#4** If the clan council decides to archive any of its own channels, then no message or announce needs to be made. 
-**#5** `Hidden | Council archives` has sensitive information in past discussions from council terms and should only be viewed by current clan council members.
-**#6** `Hidden | OSRS channels` has sensitive information as past discussions from the OSRS council and should only be viewed by current clan council members.
-**#7** Other categories can be open to view for the public and any channel can be unarchived if the Clan Council deems that necessary.
-**#8** Everyone's name in the server must be their in-game name. In case of having multiple, use | to give them both names. For example *Dak Name | Iron Name*.
-**#9** Changes to the server structure can be done, but they must pass Clan Council vote. Overhauls must the thoroughly discussed to avoid changing the server every new term.
\ No newline at end of file
+**4** If the clan council decides to archive any of its own channels, then no message or announce needs to be made. 
+**5** `Hidden | Council archives` has sensitive information in past discussions from council terms and should only be viewed by current clan council members.
+**6** `Hidden | OSRS channels` has sensitive information as past discussions from the OSRS council and should only be viewed by current clan council members.
+**7** Other categories can be open to view for the public and any channel can be unarchived if the Clan Council deems that necessary.
+**8** Everyone's name in the server must be their in-game name. In case of having multiple, use | to give them both names. For example *Dak Name | Iron Name*.
+**9** Changes to the server structure can be done, but they must pass Clan Council vote. Overhauls must the thoroughly discussed to avoid changing the server every new term.
\ No newline at end of file
diff --git a/messages/council_rules/5.txt b/messages/council_rules/5.txt
index 84b6eee..dc28bf1 100644
--- a/messages/council_rules/5.txt
+++ b/messages/council_rules/5.txt
@@ -1,9 +1,9 @@
-**#10** The <@&810567528228061236> role (grants access to event_participation) is a temporary role granted for someone when they host a clan event, but needs to be taken away if they haven't hosted an event in the past 2 months.
-**#11** Server owner must create and manage the voting channel for the next term following the dates expressed in <#668483654694993928> and the sub rules bellow.
-**#12** Roles that members get as a reward from clan events are always temporary rewards to avoid having too many roles in the server that have 1-2 people and no purpose.
-**#13** All bots in the Dakiny server are of one of the following categories and bots that don't fall into those categories cannot be added to the server:
-**a.** Runescape (RS3 and/or OSRS and any new game under the Runescape umbrella) related bots such as RuneInfo, SuityBot and Friendliness.net.
-**b.** Music related bots such as FreddyBoat and Rythm.
-**c.** Management related bots such as Carl bot and Ticket Bot.
- **#13.1** Examples of bots that are not allowed in the server as they don't fit the theme (runescape) and would clutter the server, such as Tamamo bot, Meme bots, gif generation bots, Purplebot (or any other private bots made by clan members), Pokemon bots, other games related bots, etc.
-**#14.** DO NOT modify permissions on <#802355370260693013>, unless it’s to add/remove persons as voted on. It is intentionally not synced with the Clan Council category.
\ No newline at end of file
+**10** The <@&810567528228061236> role (grants access to event_participation) is a temporary role granted for someone when they host a clan event, but needs to be taken away if they haven't hosted an event in the past 2 months.
+**11** Discord Manager must create and manage the voting channel for the next term following the dates expressed in <#668483654694993928> and the sub rules bellow.
+**12** Roles that members get as a reward from clan events are always temporary rewards to avoid having too many roles in the server that have 1-2 people and no purpose.
+**13** All bots in the Dakiny server are of one of the following categories and bots that don't fall into those categories cannot be added to the server:
+  **13.1** Runescape (RS3 and/or OSRS and any new game under the Runescape umbrella) related bots such as RuneInfo, SuityBot and Friendliness.net.
+  **13.2** Music related bots such as FreddyBoat and Rythm.
+  **13.3** Management related bots such as Carl bot and Ticket Bot.
+**14** Examples of bots that are not allowed in the server as they don't fit the theme (runescape) and would clutter the server, such as Tamamo bot, Meme bots, gif generation bots, Purplebot (or any other private bots made by clan members), Pokemon bots, other games related bots, etc.
+**15** DO NOT modify permissions on <#802355370260693013>, unless it’s to add/remove persons as voted on. It is intentionally not synced with the Clan Council category.
\ No newline at end of file
diff --git a/messages/council_rules/6.txt b/messages/council_rules/6.txt
index d83a05e..a95cf4c 100644
--- a/messages/council_rules/6.txt
+++ b/messages/council_rules/6.txt
@@ -7,6 +7,6 @@ __**Sub rules for voting management**__
 **11.6** Once voting is done, announce the new council in the voting channel.
  **11.7** Give everyone that won the election the role <@&494624264805285889> and tell them to read: <#668085252744282112> and <#668132551059177492>. 
  **11.8** Close the voting channel for those only and start the <@&478315397033099264>  candidacy and voting.Once those are done, announce the new council in <#642729302630072320>.
- **11.9** Once finished, close the channel for <@&500877978784497684> and <@&478315397033099264> only and archieve it in the HIDDEN | VOTING ARCHIVES category.
+ **11.9** Once finished, close the channel for <@&500877978784497684> and <@&478315397033099264> only and archieve it in the `Hidden | Voting archives` category.
  **11.10** When the term ends, before giving out the server ownership, give the <@&494624264805285889> their <@&500877978784497684> roles and take the <@&500877978784497684> roles from the ones that won't be part of the council anymore.
 **11.11** Those running for High Council roles must have previously held a seat in Council within the last 12 months, else they are not eligible.
\ No newline at end of file
diff --git a/messages/council_rules/7.txt b/messages/council_rules/7.txt
index 5152f37..8ece338 100644
--- a/messages/council_rules/7.txt
+++ b/messages/council_rules/7.txt
@@ -1,11 +1,11 @@
 **__OSRS clan leadership rules__**
-**#1** The "Dakiny" OSRS clan exists as a place holder to keep the name within our control and avoid having a second clan with our name but different rules and mindset as ours.
-**#2** The  "Dakiny" OSRS clan leadership should be passed down to a clan council member that isn't RS3 Clan Leader or Discord Leader.
-**#3** To hold the "Dakiny" OSRS clan leadership, said clan council member have to:
+**1** The "Dakiny" OSRS clan exists as a place holder to keep the name within our control and avoid having a second clan with our name but different rules and mindset as ours.
+**2** The  "Dakiny" OSRS clan leadership should be passed down to a clan council member that isn't RS3 Clan Leader or Discord Manager.
+**3** To hold the "Dakiny" OSRS clan leadership, said clan council member have to:
 - have been a council member for at least one term prior to the current one;
 - have an OSRS account with authenticator and bank pin;
 - have played at least 25 hours in said account (Jagex's requirement to be a clan leader in OSRS).
-**#4** Rule of exceptions: 
-- In the case of a term which no clan council member meet the requirements in rules **#2** and **#3** simultaneously, then the Discord Leader can hold the OSRS clan leadership as an exception.  
+**4** Rule of exceptions: 
+- In the case of a term which no clan council member meet the requirements in rules **#2** and **#3** simultaneously, then the Discord Manager can hold the OSRS clan leadership as an exception.  
 - If the Discord Leader also can't hold it, then the RS3 Clan Leader can hold the OSRS clan leadership as an exception.
 - If no one in the Clan Council meet the requirements to hold the OSRS clan leadership, then the Clan Council can vote for one of the member of the <@&268011909427494913> or <@&315481884681568256> hold it for that term.
\ No newline at end of file
diff --git a/messages/pvm-guidelines/1.txt b/messages/pvm-guidelines/1.txt
index ad217ec..5ed1062 100644
--- a/messages/pvm-guidelines/1.txt
+++ b/messages/pvm-guidelines/1.txt
@@ -1,4 +1,23 @@
 **__Guidelines regarding hosting__**
 ✓ Any clan member can host PvM events. 
 ✓ The guidelines listed bellow are the bare minimum, for certain bosses like Raids and AoD, the minimum requirements are listed in their respective channels.
-✓ All participants can agree to different rules if they want. The following guidelines are for situations where nothing else was agreed upon.
\ No newline at end of file
+✓ All participants can agree to different rules if they want. The following guidelines are for situations where nothing else was agreed upon.
+
+__The host may:__ 
+✓ kick/ban from the event participants that don't follow the guidelines established here or established by the host at the start of the event/pvm encounter;
+✓ request that learners watch a guide before participating in kills,
+✓ enforce minimum gear requirements and lower them;
+✓ limit how many learners are allowed per team;
+✓ require experience for roles;
+✓ request that participants join Discord voice channel to listen, talking is never required;
+✓ change the guidelines for drops for that event before the pvm encounter start;
+✓ require above the minimum requirements for certain special kills like: speed kills, feats or challenge kills;
+✓ require a player to pay for a teammate's death cost, if said player intentionally (or by negligence) caused the death of a teammate;
+✓ allow non-event-participants to join voice channel to hear or watch stream, as long as it doesn't disrupt the event;
+✓ moderate the voice channel during the pvm encounter/event and ask participants to keep non-pvm related chatter to a minimum depending on the boss and learners that are present.
+
+__Minimum Requirements for any boss hosted in this server__
+✓ t80 weapons (Zaryte bow, Strykebow, Chaotic weapons, Royal crossbow, Virtus wand/book, attuned crystal weapons, ...)
+✓ t70 dps prayers (Augury, Piety, Rigour, or Sanctity)
+✓ Stat boost potion (Super warmaster potion or super/extreme potion of your style)
+✓ t70 **power** armor (Subjugation, Armadyl, Bandos or DeathDealer)
\ No newline at end of file
diff --git a/messages/pvm-guidelines/2.txt b/messages/pvm-guidelines/2.txt
index 02b2c14..b1f1d15 100644
--- a/messages/pvm-guidelines/2.txt
+++ b/messages/pvm-guidelines/2.txt
@@ -1,12 +1,14 @@
-__The host may:__ 
-✓ kick/ban from the event participants that don't follow the guidelines established here or established by the host at the start of the event/pvm encounter;
-✓ request that learners watch a guide before participating in kills,
-✓ enforce minimum gear requirements and lower them;
-✓ limit how many learners are allowed per team;
-✓ require experience for roles;
-✓ request that participants join Discord voice channel to listen, talking is never required;
-✓ change the guidelines for drops for that event before the pvm encounter start;
-✓ require above the minimum requirements for certain special kills like: speed kills, feats or challenge kills;
-✓ require a player to pay for a teammate's death cost, if said player intentionally (or by negligence) caused the death of a teammate;
-✓ allow non-event-participants to join voice channel to hear or watch stream, as long as it doesn't disrupt the event;
-✓ moderate the voice channel during the pvm encounter/event and ask participants to keep non-pvm related chatter to a minimum depending on the boss and learners that are present.
\ No newline at end of file
+__Voice chat guidelines for PvM__
+✓ Follow all the rules listed in clan-rules.
+✓ The following channels are exclusive for PvM encounters: Bossing, Duo, Trio, Quad, AoD, Large PVM/Mass, and Teaching.
+✓ If you are not participating in the PvM encounter, do not join a PvM exclusive channel, unless invited by the host.
+✓ If someone is teaching a boss in voice chat, do not interrupt them or speak over them. Please allow them to finish speaking before adding any input.
+
+__Drops and split guidelines__
+✓ For Raids and Croesus all drops are keeps.
+✓ For Vorago, all energy are split. If an uneven number is dropped, then the extra energy is split between bomb tank and base tank.
+✓ For any other bossing, unless stated otherwise previously by the host or in the event post, all drops are: split if rare, keep if common.
+✓ In case of doubled rare drop, the first is split among the participants, the second is kept by whoever rolled the drop.
+__PvM with Ironman Accounts__
+✓ By default, Irons keep drops while mains split per above guidelines.
+✓ If loot is not individual, lootshare should be enabled (i.e. rago, kk, nex, etc.)
\ No newline at end of file
diff --git a/messages/pvm-guidelines/3.txt b/messages/pvm-guidelines/3.txt
deleted file mode 100644
index 4377a0c..0000000
--- a/messages/pvm-guidelines/3.txt
+++ /dev/null
@@ -1,5 +0,0 @@
-__Minimum Requirements for any boss hosted in this server__
-✓ t80 weapons (Zaryte bow, Strykebow, Chaotic weapons, Royal crossbow, Virtus wand/book, attuned crystal weapons, ...)
-✓ t70 dps prayers (Augury, Piety, Rigour, or Sanctity)
-✓ Stat boost potion (Super warmaster potion or super/extreme potion of your style)
-✓ t70 **power** armor (Subjugation, Armadyl, Bandos or DeathDealer)
\ No newline at end of file
diff --git a/messages/pvm-guidelines/4.txt b/messages/pvm-guidelines/4.txt
deleted file mode 100644
index 16b0236..0000000
--- a/messages/pvm-guidelines/4.txt
+++ /dev/null
@@ -1,5 +0,0 @@
-__Voice chat guidelines for PvM__
-✓ Follow all the rules listed in clan-rules.
-✓ The following channels are exclusive for PvM encounters: Bossing, Duo, Trio, Quad, AoD, Large PVM/Mass, and Teaching.
-✓ If you are not participating in the PvM encounter, do not join a PvM exclusive channel, unless invited by the host.
-✓ If someone is teaching a boss in voice chat, do not interrupt them or speak over them. Please allow them to finish speaking before adding any input.
\ No newline at end of file
diff --git a/messages/pvm-guidelines/5.txt b/messages/pvm-guidelines/5.txt
deleted file mode 100644
index cd92b66..0000000
--- a/messages/pvm-guidelines/5.txt
+++ /dev/null
@@ -1,8 +0,0 @@
-__Drops and split guidelines__
-✓ For Raids and Croesus all drops are keeps.
-✓ For Vorago, all energy are split. If an uneven number is dropped, then the extra energy is split between bomb tank and base tank.
-✓ For any other bossing, unless stated otherwise previously by the host or in the event post, all drops are: split if rare, keep if common.
-✓ In case of doubled rare drop, the first is split among the participants, the second is kept by whoever rolled the drop.
-__PvM with Ironman Accounts__
-✓ By default, Irons keep drops while mains split per above guidelines.
-✓ If loot is not individual, lootshare should be enabled (i.e. rago, kk, nex, etc.)
\ No newline at end of file