Update dodo.py

Co-authored-by: Alexis Métaireau <alexis@freedom.press>

docs/developer/doit.md

@@ -1,7 +1,7 @@
 # Using the Doit Automation Tool
 
 Developers can use the [Doit](https://pydoit.org/) automation tool to create
-release artifacts. The purpose of the tool is to automate our manual release
+release artifacts. The purpose of the tool is to automate the manual release
 instructions in `RELEASE.md` file. Not everything is automated yet, since we're
 still experimenting with this tool. You can find our task definitions in this
 repo's `dodo.py` file.
@@ -14,7 +14,7 @@ We picked Doit out of the various tools out there for the following reasons:
   applicable, it's easy to issue shell commands as well.
 * **File targets:** Doit borrows the file target concept from Makefiles. Tasks
   can have file dependencies, and targets they build. This makes it easy to
-  define a dependency graph (DAG) for tasks.
+  define a dependency graph for tasks.
 * **Hash-based caching:** Unlike Makefiles, doit does not look at the
   modification timestamp of source/target files, to figure out if it needs to
   run them.  Instead, it hashes those files, and will run a task only if the

dodo.py

@@ -29,7 +29,7 @@ PARAM_APPLE_ID = {
     "name": "apple_id",
     "long": "apple-id",
     "default": APPLE_ID,
-    "help": "The Apple developer ID that will be used for signing the .dmg",
+    "help": "The Apple developer ID that will be used to sign the .dmg",
 }
 
 PARAM_USE_CACHE = {