prettify

Author: badboy

scripts/prettier_fix.sh

@@ -3,4 +3,4 @@ export TERM=xterm-color
 
 SEARCH_PATH=${@:-'src/**/*.md'}
 
-npx prettier --write --loglevel warn $SEARCH_PATH
+npx prettier --write --log-level warn $SEARCH_PATH

src/concepts/analysis_gotchas.md

@@ -318,19 +318,16 @@ The build id format for Firefox Desktop has been very stable over time thus far,
 #### If you still need to do side-by-side comparisons, be aware that significant discrepancies will occur due to a variety of factors:
 
 1. **Bucket Discrepancies (Histograms)**
-
    - **Legacy Telemetry**: Fewer buckets; Uses a fixed number of buckets depending on histogram type.
    - **Glean**: More buckets; Uses an algorithmically-generated number of buckets depending on the metric's distribution type.
    - **Result**: The distributions and percentiles can look different in GLAM even when measuring the same underlying data because the histogram bounds and number of buckets do not match.
 
 2. **Cross-Process vs. Per-Process Collection**
-
    - **Legacy Telemetry**: Often collects data per process (e.g., main, content, etc.) and can send data differently depending on the process.
    - **Glean**: Consolidates measurements across multiple processes.
    - **Result**: Aggregated Glean data may appear larger or differently distributed compared to Legacy data, because it merges what Legacy would treat as separate process-specific measurements.
 
 3. **Ping Differences ("baseline" & "metrics" Pings in Glean, "main" pings in Legacy Telemetry)**
-
    - **Legacy Telemetry**: Typically sends one primary ping type (e.g., the “main” ping) for most data.
    - **Glean**: Splits data into multiple ping types (e.g., a “baseline” ping, a “metrics” ping, etc.).
    - **Result**: The same metric can appear to have more frequent updates or different submission times in Glean if it is reported in multiple pings.

src/concepts/glean/glean.md

@@ -78,7 +78,6 @@ This includes previously manual and error-prone steps such as updating the ping
 - [Integrate the Glean SDK](https://mozilla.github.io/glean/book/user/adding-glean-to-your-project/index.html) into your product.
 - [Use Looker](https://mozilla.cloud.looker.com/) to build Explores and Dashboards using your product's datasets.
 - If Looker does not provide the necessary Explores you can resort to [using Redash](https://sql.telemetry.mozilla.org/) to write SQL queries & build dashboards using your products datasets, e.g.:
-
   - `org_mozilla_fenix.baseline`
   - `org_mozilla_fenix.events`
   - `org_mozilla_fenix.metrics`

src/tools/projects.md

@@ -139,4 +139,3 @@ starting a new project using anything in this section.
 
 | Name and repo | Description |
 | ------------- | ----------- |
-

src/tools/stmo.md

@@ -73,7 +73,6 @@ You should see a `clients_last_seen` entry (appearing as `telemetry.clients_last
 - Introspect the available columns
 
   Click `telemetry.clients_last_seen` in the schema browser to display the columns that are available in the table. The following columns are of interest for this query:
-
   - `country`
   - `days_since_seen`
   - `submission_date`.