Fix typo.

Author: ggbecker

_posts/2023-04-25-mrac.md

@@ -114,7 +114,7 @@ This can be very difficult to achieve exhaustively, but a partial and good enoug
 ###  Polymorphic rules
 
 Rules that try to do two things don't sound like a good idea, but what if those two things would heavily overlap?
-Great candidats for polymorphism are changes when component configuration doesn't change, as it is the way of how to achieve this configuration that does.
+Great candidates for polymorphism are changes when component configuration doesn't change, as it is the way of how to achieve this configuration that does.
 In cases like this, a rule can get a polymorphic remediation and keep the `CCE` identifier if it has one, as `CCE`s don't change if the configuration stays the same.
 
 For instance, the rule [no_empty_passwords](https://github.com/ComplianceAsCode/content/tree/master/linux_os/guide/system/accounts/accounts-restrictions/password_storage/no_empty_passwords) also mentioned earlier, has polymorphic Bash remediation and a rather simple OVAL check.