fixed an ommited word.md (#752)

Signed-off-by: Denis Borisov <[email protected]>

website/content/contributors/getting-started.md

@@ -103,7 +103,7 @@ These issues are typically well-defined and relatively easy to implement. They c
 
 Pull requests are a way to propose changes to a project. When you submit a pull request, you ask the project maintainers to review your code or document changes and consider merging it into the main codebase. To create a pull request, you'll need to fork the project, make your changes, and then submit the pull request through the project's website or Git hosting platform.
 
-Code reviews are essential to the software development process as they help catch potential issues before they become problems. It's important to remember that code reviews are not personal and should not be taken as criticism of the contributor. Instead, they allow contributors to learn from each other and improve their skills. Code reviews can be especially beneficial for beginner contributors as they can learn from more experienced contributors about potential issues with their code and how to improve it. Code reviews are a valuable mechanism for learning and improving code quality. Code is about working together to produce the best code or documentation.
+Code reviews are essential to the software development process as they help catch potential issues before they become problems. It's important to remember that code reviews are not personal and should not be taken as criticism of the contributor. Instead, they allow contributors to learn from each other and improve their skills. Code reviews can be especially beneficial for beginner contributors as they can learn from more experienced contributors about potential issues with their code and how to improve it. Code reviews are a valuable mechanism for learning and improving code quality. Code review is about working together to produce the best code or documentation.
 
 It's important to remember that things take some time when it comes to code reviews. Asynchronous communication is the norm for code reviews, and it can take time for reviewers to provide feedback. Additionally, factors outside the review process may impact response times, such as timezone differences, country-specific holidays, and team stress related to releases or deadlines. It's not uncommon for contributors to become frustrated when they are unaware of these factors and feel that they are not being taken seriously. However, it's essential to maintain open communication and trust between contributors and reviewers, as this can help alleviate any misunderstandings and ensure that the review process remains productive and efficient.