fix: Typos

Author: brnhensley

CONTRIBUTING.md

@@ -75,7 +75,7 @@ When contributing to this repository, please ensure that your commit messages ad
   * `style` - changes that do not affect the meaning of the code (e.g. formatting, white-space, etc.)
   * `test` - adding new tests or modifying existing tests
 * Use the imperative, present tense (e.g. "add feature" instead of "added feature")
-* Optionally, include a scope in parantheses after the type to indicate which part of the repository is affected (e.g. `feat(instrumentation): add support for Prisma Client`)
+* Optionally, include a scope in parentheses after the type to indicate which part of the repository is affected (e.g. `feat(instrumentation): add support for Prisma Client`)
 
 Please note that we use the [Squash and Merge](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges#squash-and-merge-your-commits) method when merging Pull Requests into the main branch. We do not use the original commit messages from each individual commit. Instead, we use the Pull Request title as the commit message for the squashed commit, and as such, require that the Pull Request title adheres to our Conventional Commit standards. Any additional documentation or information relevant to the release notes should be added to the "optional extended description" section of the squash commit on merge.
 

bin/create-github-release.js

@@ -68,7 +68,7 @@ async function createRelease() {
     console.log('*** Full Run Successful ***')
   } catch (err) {
     if (err.status && err.status === 404) {
-      console.log('404 status error detected. For octokit, this may mean insuffient permissions.')
+      console.log('404 status error detected. For octokit, this may mean insufficient permissions.')
       console.log('Ensure you have a valid GITHUB_TOKEN set in your env vars.')
     }
 

bin/pending-prs.js

@@ -134,11 +134,11 @@ async function findMergedPRs(repo, ignoredLabels) {
 
   const filteredPullRequests = mergedPullRequests.filter((pr) => {
     // Find all PRs without an ignored label
-    const withIngored = pr.labels.some(({ name }) => ignoredLabels.includes(name))
+    const withIgnored = pr.labels.some(({ name }) => ignoredLabels.includes(name))
 
     // Sometimes the commit for the PR the tag is set to has an earlier time than
     // the PR merge time and we'll pull in release note PRs. Filters those out.
-    return pr.merge_commit_sha !== tag.commit.sha && !withIngored
+    return pr.merge_commit_sha !== tag.commit.sha && !withIgnored
   })
 
   console.log(`Found ${filteredPullRequests.length} PRs not yet released.`)

documentation/function-wrapping.md

@@ -21,7 +21,7 @@ const newrelic = require('newrelic');
 const agent = require.cache.__NR_cache.agent;
 const Shim = require('newrelic/lib/shim/shim');
 
-// do the same fnApply/apply shenangins as the shim library
+// do the same fnApply/apply shenanigans as the shim library
 // https://github.com/newrelic/node-newrelic/blob/v7.1.3/lib/shim/shim.js#L17-L19
 const fnApply = Function.prototype.apply
 

documentation/nextjs/faqs/instrument-third-party-libraries.md

@@ -2,7 +2,7 @@
 
 Q: How can I get instrumentation to load for 3rd party libraries within my Next.js application like mysql, mongodb, pino, winston, etc?  
 
-A: Typically the New Relic Node.js agent auto-instruments all supported [3rd party libraries](https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent/#instrument).  Next.js, however, bundles your project and code spilts between server and client side via webpack.  To get auto-instrumentation to work, you must externalize all libraries within webpack.  
+A: Typically the New Relic Node.js agent auto-instruments all supported [3rd party libraries](https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent/#instrument).  Next.js, however, bundles your project and code splits between server and client side via webpack.  To get auto-instrumentation to work, you must externalize all libraries within webpack.  
 
 ## Externalize 3rd party libraries in webpack
 

examples/instrumentation.md

@@ -7,7 +7,7 @@ We have moved our examples and tutorials over to [newrelic-node-examples](https:
 * [instrumentWebframework](https://github.com/newrelic/newrelic-node-examples/tree/main/custom-instrumentation/instrument-webframework) - example application that uses the [newrelic.instrumentWebframework API](https://newrelic.github.io/node-newrelic/API.html#instrumentWebframework) and associated [WebFramework shim API](https://newrelic.github.io/node-newrelic/WebFrameworkShim.html) to instrument a hypothetical web framework
 * [attributesAndEvents](https://github.com/newrelic/newrelic-node-examples/tree/main/custom-instrumentation/attributes-and-events) - example application that demonstrates how to share custom [attributes](https://newrelic.github.io/node-newrelic/API.html#addCustomAttribute) and [events](https://newrelic.github.io/node-newrelic/API.html#recordCustomEvent)
 * [backgroundTransactions](https://github.com/newrelic/newrelic-node-examples/tree/main/custom-instrumentation/background-transactions) - example application that uses the newrelic API to create [background transactions](https://newrelic.github.io/node-newrelic/API.html#startBackgroundTransaction)
-* [segments](https://github.com/newrelic/newrelic-node-examples/tree/main/custom-instrumentation/segments) - example application that demonstrates how to use the [newrelic.startSegment API](https://newrelic.github.io/node-newrelic/API.html#startSegment) in a variety of cases: callback-based, promise-based, asyncronously, and syncronously
+* [segments](https://github.com/newrelic/newrelic-node-examples/tree/main/custom-instrumentation/segments) - example application that demonstrates how to use the [newrelic.startSegment API](https://newrelic.github.io/node-newrelic/API.html#startSegment) in a variety of cases: callback-based, promise-based, asynchronously, and synchronously
 * [distributed tracing](https://github.com/newrelic/newrelic-node-examples/tree/main/custom-instrumentation/distributed-tracing) - example application that demonstrates distributed tracing
 
 To request additional examples, please [file an issue](https://github.com/newrelic/node-newrelic/issues)!

lib/agent.js

@@ -444,7 +444,7 @@ Agent.prototype._scheduleHarvests = function _scheduleHarvests(shouldImmediately
 
   const agent = this
 
-  // For data collection that streams immediately, dont delay capture/sending until
+  // For data collection that streams immediately, don't delay capture/sending until
   // the harvest of everything else has completed.
   agent.startStreaming()
 
@@ -564,7 +564,7 @@ Agent.prototype._resetCustomEvents = function resetCustomEvents() {
  * @fires Agent#harvestFinished
  */
 Agent.prototype.harvestSync = function harvestSync() {
-  logger.trace('Peparing to harvest.')
+  logger.trace('Preparing to harvest.')
 
   if (!this.collector.isConnected()) {
     throw new Error('Sync harvest not connected/enabled!')

lib/collector/remote-method.js

@@ -260,7 +260,7 @@ RemoteMethod.prototype._safeRequest = function _safeRequest(options) {
     level = 'info'
   }
 
-  // check if trace is enabled or audit log(aka info in this case) before attemping
+  // check if trace is enabled or audit log(aka info in this case) before attempting
   // to get the body length or parse the path with redacted key
   if (logger.traceEnabled() || level === 'info') {
     const logBody = Buffer.isBuffer(options.body) ? 'Buffer ' + options.body.length : options.body

lib/config/default.js

@@ -323,7 +323,7 @@ defaultConfig.definition = () => {
        */
       diagnostics: {
         formatter: boolean,
-        deafult: false
+        default: false
       }
     },
     audit_log: {
@@ -1145,7 +1145,7 @@ defaultConfig.definition = () => {
       /**
        * Controls whether the agent will generate spans for in-process actions.
        * When disabled, this will only create spans for entry and exit spans.
-       * entry spans - initial actions for web servers and messsage queue consumption.
+       * entry spans - initial actions for web servers and message queue consumption.
        * exit spans - all outgoing calls to external services(external and database calls)
        */
       in_process_spans: {
@@ -1399,7 +1399,7 @@ defaultConfig.definition = () => {
     /**
      * Obfuscates URL parameters
      * for outgoing and incoming requests
-     * for distrubuted tracing attributes - both transaction and span attributes
+     * for distributed tracing attributes - both transaction and span attributes
      * for transaction trace transaction details
      */
     url_obfuscation: {
@@ -1429,7 +1429,7 @@ defaultConfig.definition = () => {
 
         /**
          * A string containing a replacement value for URL parameters
-         * can contain refferences to capture groups in the pattern
+         * can contain references to capture groups in the pattern
          */
         replacement: {
           default: ''
@@ -1499,7 +1499,7 @@ defaultConfig.definition = () => {
       },
 
       /**
-       * Unique test identifier when runnning IAST with CI/CD
+       * Unique test identifier when running IAST with CI/CD
        */
       iast_test_identifier: '',
 

lib/config/hsm.js

@@ -71,7 +71,7 @@ const REDACT_BEFORE_SEND = new Set([
   'certificates' // should be public but in case user mistake and also these are huge
 ])
 
-// process.domain needs to be stripped befeore sending
+// process.domain needs to be stripped before sending
 const REMOVE_BEFORE_SEND = new Set(['domain'])
 
 exports.HIGH_SECURITY_SETTINGS = HIGH_SECURITY_SETTINGS