Update doc/contributing/maintaining/maintaining-dependencies.md

Co-authored-by: Aviv Keller <telavivkeller@gmail.com>

doc/contributing/maintaining/maintaining-dependencies.md

@@ -126,16 +126,16 @@ can be added by:
   paste one of the existing entries and then update to match the
   import name for the dependency and the #define generated.
 
-* if the version of the dependency is reported in process.versions,
-  update src/node\_metadata.h and src/node\_metadata.cc so that the
+* if the version of the dependency is reported in `process.versions`,
+  update `src/node_metadata.h` and `src/node_metadata.cc` so that the
   version is not reported when the dependency is externalized.
   Not reporting the version is better than incorrectly reporting
-  the version of the dependency bundled with Node.js instead of the
-  version for the externalized depenency. Use one of the existing
-  externalized dependencies like undici as an example of how to
-  do that. Make sure to run the tests with the dependency externalized
-  as the tests will also need to be updated to handle this properly.
-  For example, test/parallel/test-process-versions.js.
+  the version of the dependency bundled with Node.js, instead of the
+  version for the externalized dependency. Use one of the existing
+  externalized dependencies, like undici, as an example of how to
+  update these files correctly. Make sure to run the tests with the
+  dependency externalized, as the tests will also need to be updated
+  to handle this properly.
 
 ## Supporting non-externalized dependencies with JavaScript code