doc: fix some typos in deprecations.md and vm.md

PR-URL: #21569
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Weijia Wang <starkwang@126.com>

doc/api/deprecations.md

@@ -979,8 +979,8 @@ because it also made sense to interpret the value as the number of bytes
 read by the engine, but is inconsistent with other streams in Node.js that
 expose values under these names.
 
-<a id="DEP00XX"></a>
-### DEP00XX: vm.Script cached data
+<a id="DEP0110"></a>
+### DEP0110: vm.Script cached data
 
 Type: Documentation-only
 
@@ -1031,7 +1031,7 @@ The option `produceCachedData` has been deprecated. Use
 [`process.env`]: process.html#process_process_env
 [`punycode`]: punycode.html
 [`require.extensions`]: modules.html#modules_require_extensions
-[`script.createCachedData()`]: vm.html#vm_script_create_cached_data
+[`script.createCachedData()`]: vm.html#vm_script_createcacheddata
 [`setInterval()`]: timers.html#timers_setinterval_callback_delay_args
 [`setTimeout()`]: timers.html#timers_settimeout_callback_delay_args
 [`tls.CryptoStream`]: tls.html#tls_class_cryptostream

doc/api/vm.md

@@ -435,7 +435,7 @@ changes:
     `cachedData` property of the returned `vm.Script` instance.
     The `cachedDataProduced` value will be set to either `true` or `false`
     depending on whether code cache data is produced successfully.
-    This option is deprecated in favor of `script.createCachedData`.
+    This option is deprecated in favor of `script.createCachedData()`.
 
 Creating a new `vm.Script` object compiles `code` but does not run it. The
 compiled `vm.Script` can be run later multiple times. The `code` is not bound to