Fix spacing, future tense and word abbreviation in documentation related to...
What does this MR do?
Fix spacing, future tense and word abbreviation in documentation related to audit event.
Describe in detail what your merge request does and why.
Resolves issues highlighted by the linter. One future tense issue highlighted by linter was not fixed as the use of future tense was appropriate; there is reference to an update in the future, therefore language was not changed.
Are there any risks involved with the proposed change? What additional test coverage is introduced to offset the risk?
No.
Please keep this description up-to-date with any discussion that takes place so that reviewers can understand your intent. This is especially important if they didn't participate in the discussion.
-->
Screenshots
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team