doc: use present tense in error messages

Error messages are a mix of present and past tense. They should be mostly or entirely present tense. This eliminates the past tense constructions "was found" and "were found". PR-URL: #35164 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Denys Otrishko <[email protected]> Reviewed-By: Derek Lewis <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
nodejs · Sep 14, 2020 · 9d12c14 · 9d12c14
1 parent b569376
commit 9d12c14
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/doc/api/errors.md b/doc/api/errors.md
@@ -1381,7 +1381,7 @@ specifier.
 <a id="ERR_INVALID_PACKAGE_CONFIG"></a>
 ### `ERR_INVALID_PACKAGE_CONFIG`
 
-An invalid [`package.json`][] file was found which failed parsing.
+An invalid [`package.json`][] file failed parsing.
 
 <a id="ERR_INVALID_PACKAGE_TARGET"></a>
 ### `ERR_INVALID_PACKAGE_TARGET`
@@ -1611,7 +1611,7 @@ added: REPLACEME
 -->
 
 An object that needs to be explicitly listed in the `transferList` argument
-was found in the object passed to a [`postMessage()`][] call, but not provided
+is in the object passed to a [`postMessage()`][] call, but is not provided
 in the `transferList` for that call. Usually, this is a `MessagePort`.
 
 In Node.js versions prior to REPLACEME, the error code being used here was
@@ -2133,7 +2133,7 @@ import 'package-name'; // supported
 ### `ERR_VALID_PERFORMANCE_ENTRY_TYPE`
 
 While using the Performance Timing API (`perf_hooks`), no valid performance
-entry types were found.
+entry types are found.
 
 <a id="ERR_VM_DYNAMIC_IMPORT_CALLBACK_MISSING"></a>
 ### `ERR_VM_DYNAMIC_IMPORT_CALLBACK_MISSING`