Developer-Guide.md

@@ -56,7 +56,7 @@ After you are done adding a feature, make sure to run the `make check` command.
 ![Screen_Shot_2021-05-20_at_16.28.59](uploads/b1b12851d4619a4e764cec905d4e1848/Screen_Shot_2021-05-20_at_16.28.59.png)
 Let's say you imported a library and never used it, in that case, the linter will complain:
 ![Screen_Shot_2021-05-20_at_16.29.38](uploads/3f6ee4e4d535e7c54975ff6964c222d1/Screen_Shot_2021-05-20_at_16.29.38.png)
-You *have* to make sure that `make check` command doesn't return any errors because GitLab also runs that command once you push the code and we will not be merging any code until the green checkmark shows up next to your commit.
+You **have to** make sure that `make check` command doesn't return any errors because GitLab also runs that command once you push your code and we will not be merging any code until the green checkmark shows up next to your commit.
 
 ## Testing your code
 It is important to add unit tests for the code you wrote. At the moment, it is not the first priority but please write tests whenever you can. Once you have the test, you can run them with `make test` command: