From 94293b2c72bd16ff660ad25082cee8f10a69684a Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Wed, 27 May 2026 12:22:20 +0000 Subject: [PATCH] docs: fix typos, grammar, and broken markdown across docs --- OptTutorial/1-intro.mdx | 2 +- OptTutorial/3-configure-build-demo.mdx | 2 +- docs/add-enterprise-admins.mdx | 2 +- docs/akamai-cloud-monitor-logs.mdx | 2 +- docs/data-restoration.mdx | 4 +--- docs/visualize-log-data-with-graphs.mdx | 2 +- guide-to-pipeline-architecture/1--introduction.mdx | 2 +- .../july-22nd-2020-logdna-web-version-2261.mdx | 2 +- telemetry-pipelines/js-script-processor.mdx | 4 ++-- 9 files changed, 10 insertions(+), 12 deletions(-) diff --git a/OptTutorial/1-intro.mdx b/OptTutorial/1-intro.mdx index 2c18ef8..70f50c2 100644 --- a/OptTutorial/1-intro.mdx +++ b/OptTutorial/1-intro.mdx @@ -19,7 +19,7 @@ In this workshop, we will use the [OpenTelemetry Demo](https://github.com/open-t To accomplish this we will: -- Create a OpenTelemetry Log, Metric and Trace [Shared Sources](/telemetry-pipelines/shared-sources) in Mezmo +- Create an OpenTelemetry Log, Metric and Trace [Shared Sources](/telemetry-pipelines/shared-sources) in Mezmo - [Configure OpenTelemetry collector](https://github.com/braxtonj/opentelemetry-demo/mezmo-otel-config-extras.yml) with Mezmo Shared Source credentials - Explore the OpenTelemetry Logs via [Data Profiling](/telemetry-pipelines/data-profiling) - Send log data to [Mezmo Log Analysis](/docs) diff --git a/OptTutorial/3-configure-build-demo.mdx b/OptTutorial/3-configure-build-demo.mdx index ebadef8..b932d5a 100644 --- a/OptTutorial/3-configure-build-demo.mdx +++ b/OptTutorial/3-configure-build-demo.mdx @@ -12,7 +12,7 @@ Run `git clone https://github.com/open-telemetry/opentelemetry-demo` into a fold ## Step 2: Configure `src/otel-collector/otelcol-config-extras.yml` with Shared Source Credentials -Grab the URL and saved Access Keys from your Log, Metric and Trace Shared Sources (don't worry, if you didn't save the key you can always create a new one). Modify[ src/otel-collector/otelcol-config-extras.yml](https://github.com/open-telemetry/opentelemetry-demo/blob/main/src/otel-collector/otelcol-config-extras.yml) with the proper credentials and save. Note that Log, Metrics and Traces will each have their own unique URL and Access Keys. +Grab the URL and saved Access Keys from your Log, Metric and Trace Shared Sources (don't worry, if you didn't save the key you can always create a new one). Modify [src/otel-collector/otelcol-config-extras.yml](https://github.com/open-telemetry/opentelemetry-demo/blob/main/src/otel-collector/otelcol-config-extras.yml) with the proper credentials and save. Note that Log, Metrics and Traces will each have their own unique URL and Access Keys. #### Example OpenTelemetry Extras Configuration YAML diff --git a/docs/add-enterprise-admins.mdx b/docs/add-enterprise-admins.mdx index d71e67a..d2bbeb2 100644 --- a/docs/add-enterprise-admins.mdx +++ b/docs/add-enterprise-admins.mdx @@ -6,7 +6,7 @@ title: "Add Enterprise Admins" You can easily add administrators to your Enterprise on the **General** page. These admins will be able to view the Enterprise Dashboard, manage child organizations, and configure sign-in options. -> When you add a admins for your enterprise, they do not gain any admin privileges for the child organizations in your enterprise. You must be directly added to the organization as an admin to gain additional organization admin capabilities. +> When you add an admin for your enterprise, they do not gain any admin privileges for the child organizations in your enterprise. You must be directly added to the organization as an admin to gain additional organization admin capabilities. 1. Log in to [the Mezmo Web App](http://app.mezmo.com/). 2. Select your organization at the bottom of the left-hand navigation. diff --git a/docs/akamai-cloud-monitor-logs.mdx b/docs/akamai-cloud-monitor-logs.mdx index 8b784da..b7b2a36 100644 --- a/docs/akamai-cloud-monitor-logs.mdx +++ b/docs/akamai-cloud-monitor-logs.mdx @@ -41,7 +41,7 @@ You can find information for each of your datasets in these log entries: | | | | ---- | ---- | | **Base Log Line Data** | `meta.*` | -| **Geographic Data** | `geo.*' | +| **Geographic Data** | `geo.*` | | **HTTP 1.0** | `http.*` | | **Message Exchange Data** | `http.*` | | **Network Data 1.0** | `network.*` | diff --git a/docs/data-restoration.mdx b/docs/data-restoration.mdx index c079c7b..6c1d7ef 100644 --- a/docs/data-restoration.mdx +++ b/docs/data-restoration.mdx @@ -11,9 +11,7 @@ Mezmo's Log Data Restoration feature provides a way to re-ingest, or restore, ar - On [AWS S3](/docs/export-logs-to-external-storage), object ownership needs to be set to [object writer](https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-ownership-new-bucket.html#:~:text=Object%20writer%20(default)) - The Mezmo system requires **read** access to the stored logs - By default, each restoration task will be ingested for the same period of time as your normal logs -- Data Restoration is included in [ -the Pro, and Enterprise plans -](https://www.mezmo.com/pricing) +- Data Restoration is included in [the Pro, and Enterprise plans](https://www.mezmo.com/pricing) ## Create a New Log Data Restoration Task diff --git a/docs/visualize-log-data-with-graphs.mdx b/docs/visualize-log-data-with-graphs.mdx index 1437458..7f83f7a 100644 --- a/docs/visualize-log-data-with-graphs.mdx +++ b/docs/visualize-log-data-with-graphs.mdx @@ -12,7 +12,7 @@ Boards ### Filtering -You can filter your board by entering an query into **Filter this board**. Filter the board using [search](/docs/search-and-filter). +You can filter your board by entering a query into **Filter this board**. Filter the board using [search](/docs/search-and-filter). ### Date and Time diff --git a/guide-to-pipeline-architecture/1--introduction.mdx b/guide-to-pipeline-architecture/1--introduction.mdx index f1154ec..f1938a4 100644 --- a/guide-to-pipeline-architecture/1--introduction.mdx +++ b/guide-to-pipeline-architecture/1--introduction.mdx @@ -15,7 +15,7 @@ In this workshop, we will be exploring telemetry data produced with the [OpenTel To accomplish this we will: -1. Create a OpenTelemetry Log, Metric, and Trace [Shared Source](/telemetry-pipelines/shared-sources) in Mezmo. +1. Create an OpenTelemetry Log, Metric, and Trace [Shared Source](/telemetry-pipelines/shared-sources) in Mezmo. 2. [Configure OpenTelemetry collector](https://github.com/mezmo/opentelemetry-demo/mezmo-otel-config-extras.yml) with Mezmo Shared Source credentials. 3. Explore the OpenTelemetry Logs via [Data Profiling](/telemetry-pipelines/data-profiling) 4. Send log data to [Mezmo Log Analysis](/docs) diff --git a/log-analysis-changelog/july-22nd-2020-logdna-web-version-2261.mdx b/log-analysis-changelog/july-22nd-2020-logdna-web-version-2261.mdx index f789395..d9254ad 100644 --- a/log-analysis-changelog/july-22nd-2020-logdna-web-version-2261.mdx +++ b/log-analysis-changelog/july-22nd-2020-logdna-web-version-2261.mdx @@ -10,7 +10,7 @@ title: "July 22nd, 2020 - LogDNA Web Version 2.26.0" ## Enhancements - Improved error handling when histogram fails to load. -- Improved when an timeout happens during a search, existing search results will still show in the log viewer. +- Improved when a timeout happens during a search, existing search results will still show in the log viewer. ## Changelog Categories * Added (new features) diff --git a/telemetry-pipelines/js-script-processor.mdx b/telemetry-pipelines/js-script-processor.mdx index 91a74be..5a22581 100644 --- a/telemetry-pipelines/js-script-processor.mdx +++ b/telemetry-pipelines/js-script-processor.mdx @@ -99,8 +99,8 @@ String operations supported follow the standard Javascript conventions. | + | Concatenates two strings together | | .endsWith(substring) | Checks whether a string ends with `substring.` | | .startsWith(substring) | Checks whether a string starts with `substring.` | -| .at() | Retrieve an character at the specific index from a string (more readable) | -| .charAt() | Retrieve an character at the specific index from a string | +| .at() | Retrieve a character at the specific index from a string (more readable) | +| .charAt() | Retrieve a character at the specific index from a string | | .indexOf() | Return the first index of a value in a string | | .lastIndexOf() | Return the last index of a value in a string | | .length | Returns the number of characters in a string\n\n\n\n_Note that to avoid collisions with a field name of_ `.length`_the function checks to ensure that field does not exist first. If it does, it will return the value of the field, not the computed length._ |