@@ -61,7 +61,7 @@ A considerable amount of maintainer effort can go into producing documentation
6161that makes it easier for someone to contribute.
6262
6363Some projects are less affected than others. That is usually related to how well
64- do the potential contributors know the practices used by the project. Still, if
64+ the potential contributors know the practices used by the project. Still, if
6565your project has a wide range of uses, you will quickly discover that newbie
6666contributors may hit a knowledge wall. Such a barrier will likely prevent most
6767of them from becoming active contributors. The remaining ones will flood the
@@ -81,7 +81,7 @@ three letters prefixes.
8181
8282## Using mk to propose changes to projects
8383
84- Instead of writing long list of tasks to follow, we can use a tool that tells
84+ Instead of writing a long list of tasks to follow, we can use a tool that tells
8585him what to do next. For example, ` mk ` has a built-in command named ` up(load) `
8686that aims to ease preparing a local change from being proposed to the project.
8787
@@ -95,7 +95,7 @@ status or that the testing did not leave untracked files.
9595
9696## Planned features
9797
98- - Persistent state of each command run - This means that it will know if a
98+ - A persistent state of each command run - This means that it will know if a
9999 specific command was run and if it failed or not. The state would be linked to
100100 the repository state, so modifying a tracked file would reset the state to be
101101 unknown. (#20 )
0 commit comments