Fix broken links and grammar, misc. edits

Author: sks316

advanced/list-of-log-names.md

@@ -6,7 +6,7 @@ description: On this page all the available logs are listed
 
 # List of Log Names  
 
-Logs, categorized by what they do are listed here, and are **case sensitive**. Individual logs are written in _UPPER\_CASE_, while category names (which can be used in place of individual log names, see [configuring channels](../management-commands/config.md#channels)) are _Capitalized_. Each one of them is separated by categories in the lists below. To log all events, use an asterisk (`*`). All logs require the bot to have permission to view and send messages, embed links and attach files in the respective channels. Some logs require the bot to have the "View Audit Log" permission enabled at server level.  
+Logs, categorized by what they do, are listed here and are **case sensitive**. Individual logs are written in _UPPER\_CASE_, while category names (which can be used in place of individual log names, see [configuring channels](../management-commands/config.md#channels)) are _Capitalized_. Each one of them is separated by categories in the lists below. To log all events, use an asterisk (`*`). All logs require the bot to have permission to view and send messages, embed links and attach files in the respective channels. Some logs require the bot to have the "View Audit Log" permission enabled at server level.  
 
 ## Moderation
 

management-commands/config.md

@@ -23,7 +23,7 @@ By default, a user is required to have the following permissions to use this com
 * Manage Server
 
 For more information on editing permission requirements for specific users/roles, refer to
-the [permissions tutorial](<linkToPermissionsTutorial>)
+the [permissions tutorial](../start-up/permission-tutorial.md)
 
 ## roles edit
 
@@ -68,7 +68,7 @@ MoonlightBot requires the following permissions to successfully execute this sub
 ## roles self-assignable
 
 This command allows you to set up a role to be self-assignable by users. This allows them to assign the role to
-themselves via the [`selfrole`](../role-management-commands/selfrole.md) command without needing a moderator to do it
+themselves via the [`/selfrole`](../role-management-commands/selfrole.md) command without needing a moderator to do it
 for them, and they can remove it themselves as well. It works on a vice versa basis.
 
 ```text
@@ -160,7 +160,7 @@ This command allows you to set up and manage groups for reaction roles. If the g
 
 {% hint style="info" %}
 For information on how to delete a group, refer to
-the [`reaction-roles`](../management-commands/reaction-roles.md#delete) command and for information on how to set up
+the [`/reaction-roles delete`](../management-commands/reaction-roles.md#delete) command and for information on how to set up
 reaction roles, refer to the [`Setting up reaction roles`](../start-up/setting-up-reaction-roles.md) tutorial.
 {% endhint %}
 
@@ -171,11 +171,11 @@ reaction roles, refer to the [`Setting up reaction roles`](../start-up/setting-u
 * `group`: The group to be configured or created
 * `join-only`: Prevents the user from removing their role(s)
 * `leave-only`: Prevents the user from assigning the role(s)
-* `reverse`: When the message is reacted on, it will remove the role instead of assigning it, and vice versa
+* `reverse`: When the message is reacted to, it will remove the role instead of assigning it, and vice versa
 * `max-roles`: The maximum amount of roles within the group a user can assign themselves
 * `dm-notification`: When a role is assigned/removed, the bot will message the user (true by default)
 * `freeze`: When true, the group will not function. This is a quick way to disable reaction roles without taking
-  irreversible actions, such as deleting group/message or removing reactions from the message
+  irreversible actions, such as deleting the group/message or removing reactions from the message
 * `duration`: How long the user will keep their assigned role(s)
 
 ### Required permissions
@@ -198,7 +198,7 @@ Note that you can make exceptions to the `mute-evasion-ban` via the
 ```
 
 * `mute-role`: The role to be used as the mute role which can be created via the
-  [`create-muterole`](../management-commands/create-muterole.md#create-muterole) command
+  [`/create-muterole`](../management-commands/create-muterole.md#create-muterole) command
 * `mute-evasion-ban`: If the bot should automatically ban anyone who sends a message and has the mute role to avoid
   punishment evasion
 * `locale`: The language to be used for the server
@@ -213,4 +213,4 @@ MoonlightBot requires the following permissions to successfully execute this sub
 
 *This command does not trigger any log events.*
 
-For more information on setting up those logs, refer to the [log setup tutorial](<linkToLogTutorial>)
+For more information on setting up those logs, refer to the [log setup tutorial](../README.md#logging)

management-commands/create-muterole.md

@@ -28,7 +28,7 @@ By default, a user is required to have the following permissions to use this com
 * Manage Server
 
 For more information on editing permission requirements for specific users/roles, refer to
-the [permissions tutorial](<linkToPermissionsTutorial>)
+the [permissions tutorial](../start-up/permission-tutorial.md)
 
 ## Syntax
 
@@ -44,4 +44,4 @@ the [permissions tutorial](<linkToPermissionsTutorial>)
 
 *This command does not trigger any log events.*
 
-For more information on setting up those logs, refer to the [log setup tutorial](<linkToLogTutorial>)
+For more information on setting up those logs, refer to the [log setup tutorial](../README.md#logging)

miscellaneous-commands/check-duration.md

@@ -27,7 +27,7 @@ By default, a user is required to have the following permissions to use this com
 
 *No specific permissions required*
 
-For more information on editing permission requirements for specific users/roles, refer to the [permissions tutorial](<linkToTermissionsTutorial>)
+For more information on editing permission requirements for specific users/roles, refer to the [permissions tutorial](../start-up/permission-tutorial.md)
 
 ## Syntax
 
@@ -39,4 +39,4 @@ For more information on editing permission requirements for specific users/roles
 
 *This command does not trigger any log events.*
 
-For more information on setting up those logs, refer to the [log setup tutorial](<linkToLogTutorial>)
+For more information on setting up those logs, refer to the [log setup tutorial](../README.md#logging)

miscellaneous-commands/premium.md

@@ -12,7 +12,7 @@ By default, a user is required to have the following permissions to use this com
 
 _No specific permissions required_
 
-For more information on editing permission requirements for specific users/roles, refer to the [permissions tutorial](linkToTermissionsTutorial/)
+For more information on editing permission requirements for specific users/roles, refer to the [permissions tutorial](../start-up/permission-tutorial.md)
 
 ## info
 
@@ -30,10 +30,10 @@ MoonlightBot requires the following permissions to successfully execute this sub
 
 _No specific permissions required_
 
-For more information on editing permission requirements for specific users/roles, refer to the [permissions tutorial](linkToTermissionsTutorial/)
+For more information on editing permission requirements for specific users/roles, refer to the [permissions tutorial](../start-up/permission-tutorial.md)
 
 ## Logs
 
 _This command does not trigger any log events._
 
-For more information on setting up those logs, refer to the [log setup tutorial](linkToLogTutorial/)
+For more information on setting up those logs, refer to the [log setup tutorial](../README.md#logging)

miscellaneous-commands/userconfig.md

@@ -12,7 +12,7 @@ By default, a user is required to have the following permissions to use this com
 
 _No specific permissions required_
 
-For more information on editing permission requirements for specific users/roles, refer to the [permissions tutorial](linkToPermissionsTutorial/)
+For more information on editing permission requirements for specific users/roles, refer to the [permissions tutorial](../start-up/permission-tutorial.md)
 
 ## settings
 
@@ -36,4 +36,4 @@ _No specific permissions required_
 
 _This command does not trigger any log events._
 
-For more information on setting up those logs, refer to the [log setup tutorial](linkToLogTutorial/)
+For more information on setting up those logs, refer to the [log setup tutorial](../README.md#logging)

moderation-commands/ban.md

@@ -12,7 +12,7 @@ By default, a user is required to have the following permissions to use this com
 
 * Ban Members
 
-For more information on editing permission requirements for specific users/roles, refer to the [permissions tutorial](<linkToPermissionsTutorial>)
+For more information on editing permission requirements for specific users/roles, refer to the [permissions tutorial](../start-up/permission-tutorial.md)
 
 ## Syntax
 
@@ -35,4 +35,4 @@ The user will not be notified if both `notify` and `no-infraction` are set to Tr
 
 * `BAN`: This log is triggered when a user is successfully banned. It will log the user, the responsible moderator and the reason for the ban. If an infraction is created, it will also include the infraction ID
 
-For more information on setting up those logs, refer to the [log setup tutorial](<linkToLogTutorial>)
+For more information on setting up those logs, refer to the [log setup tutorial](../README.md#logging)

moderation-commands/clean.md

@@ -1,6 +1,6 @@
 # clean
 
-This command deletes a large amount of messages from a channel, optionally limited by specifying some deletion criteria. Criteria are options that distinguish messages such as those that contain a specific phrase. Using multiple criteria will narrow the selection to only messages that fit all of them. Up to 100 messages can be deleted in a single execution of the command, and only those sent within the last 14 days.
+This command deletes a large amount of messages from a channel, optionally limited by specifying some deletion criteria. Criteria are options that distinguish messages such as those that contain a specific phrase. Using multiple criteria will narrow the selection to only messages that fit all of them. Due to limitations imposed by Discord, only messages sent within the last 14 days can be deleted.
 
 ## Required permissions
 
@@ -15,7 +15,7 @@ By default, a user is required to have the following permissions to use this com
 
 * Manage Messages
 
-For more information on editing permission requirements for specific users/roles, refer to the [permissions tutorial](/start-up/permission-tutorial.md)
+For more information on editing permission requirements for specific users/roles, refer to the [permissions tutorial](../start-up/permission-tutorial.md)
 
 ## Syntax
 
@@ -26,12 +26,12 @@ For more information on editing permission requirements for specific users/roles
 ### Options
 
 * `amount`: The amount of messages you want to clean (The default/maximum amount is 100)
-* `user`: The user you want to do delete the messages of
+* `user`: Delete messages sent by a specified user
 * `starts-with`: Delete messages that start with this value
 * `ends-with`: Delete messages that end with this value
 * `contains`: Delete messages that contain this value
-* `bots`: Whether or not to delete messages sent by bots. If this option is left blank, the bot will delete these messages, but if left as true, the bot will only delete messages by bots, otherwise it will only delete messages not sent by bots
-* `system`: Whether or not to delete system messages. System messages are messages sent by Discord, such as join or pin messages
+* `bots`: Whether or not to delete messages sent by bots. If this option is left blank, the bot will not differentiate between messages sent by users and bots. If set to false, the bot will not delete bot messages, but if set to true, the bot will only delete bot messages
+* `system`: Whether or not to delete system messages. System messages are messages sent by Discord, such as join or pin messages. This uses the same syntax as the `bots` option
 * `preserve-pins`: If true, pinned messages will not be deleted
 * `no-trace`: If true, the confirmation message will only be visible to you
 
@@ -42,7 +42,7 @@ For more information on editing permission requirements for specific users/roles
 ![An example of logs sent by the bot after a clean command execution](/.gitbook/assets/CleanLogs.png "Clean Logs")
 
 {% hint style="info" %}
-To open an HTML file, download it and open the file explorer. Double-click the file, and your computer will open a new tab in your browser to display a visualization of the messages deleted
+Rather than rendering them like other downloadable files, Discord displays the raw content of HTML files. To download the HTML file, click the download button at the bottom-right of the file display. Double-click the file, and your computer will open a new tab in your browser to display a visualization of the messages deleted.
 {% endhint %}
 
-For more information on setting up those logs, refer to the [log setup tutorial](<linkToLogTutorial>)
+For more information on setting up those logs, refer to the [log setup tutorial](../README.md#logging)

moderation-commands/infractions.md

@@ -12,7 +12,7 @@ By default, a user is required to have the following permissions to use this com
 
 * Moderate Members
 
-For more information on editing permission requirements for specific users/roles, refer to the [permissions tutorial](/start-up/permission-tutorial.md)
+For more information on editing permission requirements for specific users/roles, refer to the [permissions tutorial](../start-up/permission-tutorial.md)
 
 ## summary
 
@@ -48,7 +48,7 @@ MoonlightBot requires the following permissions to successfully execute this sub
 
 ## reason
 
-Changes the reason of the infraction. If the `reason` option is left blank, it will simply display the current one
+Changes the reason of the infraction. If the `reason` option is left blank, it will simply display the current one. You can alternatively use `%%%` to automatically copy the old content so you don't have to type it again
 
 ```text
 /infractions reason <id> [reason]
@@ -74,8 +74,8 @@ Shows a list of infractions that fit all the specified criteria, such as the mod
 * `target`: The user you want to see the infractions of
 * `moderator`: The infractions executed by a specific moderator
 * `type`: The type of the infractions you want to view
-* `before`: View infractions executed before this date
-* `after`: View infractions after this date
+* `before`: View infractions executed before this duration
+* `after`: View infractions after this duration
 
 ### Required permissions
 
@@ -87,6 +87,10 @@ MoonlightBot requires the following permissions to successfully execute this sub
 
 Deletes an infraction
 
+{% hint style="danger" %}
+This cannot be undone! Be absolutely sure that you want to delete the infraction before running this command.
+{% endhint %}
+
 ```text
 /infractions delete <id> [reason]
 ```
@@ -105,4 +109,4 @@ MoonlightBot requires the following permissions to successfully execute this sub
 * `REASON_UPDATE`: Shows the user the infraction affects, the moderator who executed it, and the updated reason
 * `INFRACTION_DELETE`: Same as above, with the reason being why the infraction was deleted
 
-For more information on setting up those logs, refer to the [log setup tutorial](<linkToLogTutorial>)
+For more information on setting up those logs, refer to the [log setup tutorial](../README.md#logging)

moderation-commands/kick.md

@@ -12,7 +12,7 @@ By default, a user is required to have the following permissions to use this com
 
 * Kick Members
 
-For more information on editing permission requirements for specific users/roles, refer to the [permissions tutorial](<linkToPermissionsTutorial>)
+For more information on editing permission requirements for specific users/roles, refer to the [permissions tutorial](../start-up/permission-tutorial.md)
 
 ## Syntax
 
@@ -35,4 +35,4 @@ The user will not be notified if both `notify` and `no-infraction` are set to Tr
 
 * `KICK`: This log is triggered when a user is kicked from a server. It will log the user, the responsible moderator and the reason for the kick. If an infraction is created, it will also include the infraction ID
 
-For more information on setting up those logs, refer to the [log setup tutorial](<linkToLogTutorial>)
+For more information on setting up those logs, refer to the [log setup tutorial](../README.md#logging)

moderation-commands/mute.md

@@ -16,7 +16,7 @@ By default, a user is required to have the following permissions to use this com
 
 * Moderate Members
 
-For more information on editing permission requirements for specific users/roles, refer to the [permissions tutorial](linkToPermissionsTutorial/)
+For more information on editing permission requirements for specific users/roles, refer to the [permissions tutorial](../start-up/permission-tutorial.md)
 
 ## Syntax
 
@@ -40,4 +40,4 @@ The user will not be notified if both `notify` and `no-infraction` are set to Tr
 
 * `MUTE`: This log is triggered when a user is muted. It will log the user, the responsible moderator and the reason for the muting. If an infraction is created, it will also include the infraction ID
 
-For more information on setting up those logs, refer to the [log setup tutorial](linkToLogTutorial/)
+For more information on setting up those logs, refer to the [log setup tutorial](../README.md#logging)

moderation-commands/softban.md

@@ -12,7 +12,7 @@ By default, a user is required to have the following permissions to use this com
 
 * Ban Members
 
-For more information on editing permission requirements for specific users/roles, refer to the [permissions tutorial](<linkToPermissionsTutorial>)
+For more information on editing permission requirements for specific users/roles, refer to the [permissions tutorial](../start-up/permission-tutorial.md)
 
 ## Syntax
 
@@ -35,4 +35,4 @@ The user will not be notified if both `notify` and `no-infraction` are set to Tr
 
 * `SOFTBAN`: This log is triggered when a user is softbanned. It will log the user, the responsible moderator and the reason for the softban. If an infraction is created, it will also include the infraction ID
 
-For more information on setting up those logs, refer to the [log setup tutorial](<linkToLogTutorial>)
+For more information on setting up those logs, refer to the [log setup tutorial](../README.md#logging)

moderation-commands/tempban.md

@@ -12,7 +12,7 @@ By default, a user is required to have the following permissions to use this com
 
 * Ban Members
 
-For more information on editing permission requirements for specific users/roles, refer to the [permissions tutorial](<linkToPermissionsTutorial>)
+For more information on editing permission requirements for specific users/roles, refer to the [permissions tutorial](../start-up/permission-tutorial.md)
 
 ## Syntax
 
@@ -37,4 +37,4 @@ The user will not be notified if both `notify` and `no-infraction` are set to Tr
 * `TEMPBAN_EXTEND`: This log is triggered when a tempban is successfully extended. It will log the user, the responsible moderator and the reason for the extended ban.
 * `BAN`: This log is triggered when a user is successfully banned. It will log the user, the responsible moderator and the reason for the ban. If an infraction is created, it will also include the infraction ID
 
-For more information on setting up those logs, refer to the [log setup tutorial](<linkToLogTutorial>)
+For more information on setting up those logs, refer to the [log setup tutorial](../README.md#logging)

moderation-commands/tempmute.md

@@ -16,7 +16,7 @@ By default, a user is required to have the following permissions to use this com
 
 * Moderate Members
 
-For more information on editing permission requirements for specific users/roles, refer to the [permissions tutorial](linkToPermissionsTutorial/)
+For more information on editing permission requirements for specific users/roles, refer to the [permissions tutorial](../start-up/permission-tutorial.md)
 
 ## Syntax
 
@@ -42,4 +42,4 @@ The user will not be notified if both `notify` and `no-infraction` are set to Tr
 * `TEMPMUTE_EXTEND`: This log is triggered when a tempmute is successfully extended. It will log the user, the responsible moderator and the reason for the extended mute.
 * `MUTE`: This log is triggered when a user is muted. It will log the user, the responsible moderator and the reason for the muting. If an infraction is created, it will also include the infraction ID
 
-For more information on setting up those logs, refer to the [log setup tutorial](linkToLogTutorial/)
+For more information on setting up those logs, refer to the [log setup tutorial](../README.md#logging)