docs: improve migrating to v5 guide

docs/migration-guides/v5.md

@@ -5,7 +5,7 @@ Assuming you are already in v4, migrating to v5 will be easy. If you are not in
 ## Overview
 
 - Support for ESLint v8
-- Drop support for Node v10 - required node version is now `^12.22.0 || ^14.17.0 || >=16.0.0`. Node v10 was EOL'd in April 2021, and ESLint v8 dropped support for it too.
+- Drop support for Node v10. Required node version is now `^12.22.0 || ^14.17.0 || >=16.0.0`. Node v10 was EOL'd in April 2021, and ESLint v8 dropped support for it too.
 - Update dependencies
 - `no-debug` is now called `no-debugging-utils`
 - `no-render-in-setup` is now enabled by default in the Angular, React & Vue configs
@@ -20,6 +20,6 @@ Assuming you are already in v4, migrating to v5 will be easy. If you are not in
 ## Steps to upgrade
 
 - `eslint-plugin-testing-library` supports both ESLint v7 and v8, so you are fine with either version
-- Make sure you are using a compatible Node version, and update it if it's not the case
-- Rename `testing-library/no-debug` to `testing-library/no-debugging-utils` if you were referencing it manually somewhere
-- Be aware of new rules enabled in Shared Configs which can lead to new reported errors
+- Making sure you are using a compatible Node version (`^12.22.0 || ^14.17.0 || >=16.0.0`), and update it if it's not the case
+- Renaming `testing-library/no-debug` to `testing-library/no-debugging-utils` if you were referencing it manually somewhere
+- Being aware of new rules enabled in Shared Configs which can lead to new reported errors