Apply suggestions from code review

Co-authored-by: Jan Černý <jcerny@redhat.com>

Author: matejak

_posts/2023-04-21-mrac.md

@@ -41,7 +41,7 @@ However, in order to be able to come with workflows that introduce an added valu
 Our team has come up with these ideas so far:
 
 - Lower the pressure on rules - enable coverage of a security requirement by more than one rule.
-- Be able to split a rule into such a set of rules easily.
+- Be able to split a rule into a set of rules easily.
 - Enhance the declarative aspect of the project.
 - Introduce a component-centric view to the project.
 - Facilitate extension of a rule's scope.
@@ -89,7 +89,7 @@ Profiles then can be [defined](https://github.com/ComplianceAsCode/content/blob/
 As an additional benefit, the assignment of rules to security controls can be reused by other parts of the project.
 
 However, this declarative concept can be extended beyond profile compositions.
-We often use constructs s.a. `{{% if product in ("rhel8", "rhel9") %}}` instead of a more generic and understandable `{{% if product.prefers_single_file_sshd_configuration %}}` or something analogous.
+We often use constructs s.a. `{{% if product in ("rhel8", "rhel9") %}}` instead of a more generic and understandable `{{% if product.prefers_single_file_sshd_configuration %}}` or similar.
 
 In other words, we shouldn't miss an opportunity to declare that a certain product has a particular property, and every other part of the content should refer to those properties rather than to product names.
 Designing such product properties in a way that is smart, doesn't get in the way and that can be reused in prose, checks and remediations is not trivial.