chore(schemas): replace e.g. with for example

Author: caugner

schemas/browsers-schema.md

@@ -1,6 +1,6 @@
 # The browser JSON schema
 
-This document helps you to understand the structure of the browser (and JavaScript runtime) data in BCD, including the browser type, a display-friendly name, release data and more. Each browser is defined by a unique identifier (e.g. `firefox` or `chrome_android`). Each browser JSON file describes exactly one browser.
+This document helps you to understand the structure of the browser (and JavaScript runtime) data in BCD, including the browser type, a display-friendly name, release data and more. Each browser is defined by a unique identifier (for example `firefox` or `chrome_android`). Each browser JSON file describes exactly one browser.
 
 Note: while NodeJS and Deno are JavaScript runtimes and not browsers, data for them is placed in `browsers`, and are included whenever we use the term "browsers".
 
@@ -56,7 +56,7 @@ A required boolean indicating whether the browser supports web extensions. A `tr
 
 ### `pref_url`
 
-An optional string containing the URL of the page where feature flags can be changed (e.g. `"about:config"` for Firefox or `"chrome://flags"` for Chrome).
+An optional string containing the URL of the page where feature flags can be changed (for example `"about:config"` for Firefox or `"chrome://flags"` for Chrome).
 
 ### `preview_name`
 
@@ -78,7 +78,7 @@ The `releases` object contains data regarding the browsers' releases, using the
 
 - An optional `release_notes` property which points to release notes. It needs to be a valid URL.
 
-- An optional `engine` property which is the name of the browser's engine. Valid values are `"Blink"`, `"EdgeHTML"`, `"Gecko"`, `"Presto"`, `"Trident"`, `"WebKit"`, and `"V8"`. This property is placed on the individual release as a browser may switch to a different engine (e.g. Microsoft Edge switched to Chrome as its base engine). If `engine` is specified, `engine_version` must also be provided.
+- An optional `engine` property which is the name of the browser's engine. Valid values are `"Blink"`, `"EdgeHTML"`, `"Gecko"`, `"Presto"`, `"Trident"`, `"WebKit"`, and `"V8"`. This property is placed on the individual release as a browser may switch to a different engine (for example Microsoft Edge switched to Chrome as its base engine). If `engine` is specified, `engine_version` must also be provided.
 
 - An optional `engine_version` property indicating the engine version used in this release. Required when `engine` is specified.
 

schemas/compat-data-schema.md

@@ -40,7 +40,7 @@ The JSON files contain [feature identifiers](#features), which are relevant for
 
 ### Feature hierarchies
 
-Each feature is identified by a unique hierarchy of strings, e.g. the `text-align` property is identified by `css.properties.text-align`.
+Each feature is identified by a unique hierarchy of strings, for example the `text-align` property is identified by `css.properties.text-align`.
 
 In the JSON file it looks like this:
 
@@ -179,10 +179,10 @@ The `__compat` object consists of the following:
   This property may be formatted using Markdown, see the rules for `notes`.
 
 - An optional `mdn_url` property which **points to an MDN reference page documenting the feature**.
-  It needs to be a valid URL, and should be the language-neutral URL (e.g. use `https://developer.mozilla.org/docs/Web/CSS/text-align` instead of `https://developer.mozilla.org/en-US/docs/Web/CSS/text-align`).
+  It needs to be a valid URL, and should be the language-neutral URL (for example use `https://developer.mozilla.org/docs/Web/CSS/text-align` instead of `https://developer.mozilla.org/en-US/docs/Web/CSS/text-align`).
 
 - An optional `spec_url` property as a URL or an array of URLs, each of which is for a specific part of a specification in which this feature is defined.
-  Each URL must contain a fragment identifier (e.g. `https://tc39.es/proposal-promise-allSettled/#sec-promise.allsettled`) or match one of the regular-expression pattern given in the JSON Schema file.
+  Each URL must contain a fragment identifier (for example `https://tc39.es/proposal-promise-allSettled/#sec-promise.allsettled`) or match one of the regular-expression pattern given in the JSON Schema file.
   Each URL must link to a specification published by a standards body or a formal proposal that may lead to such publication.
 
 - An optional `tags` property to assign tags to the feature.
@@ -494,4 +494,4 @@ The mandatory status property contains information about stability of the featur
 
 ### Localization
 
-We are planning to localize some of this data (e.g. notes, descriptions). At this point we haven't decided how or when we are going to do that. See [issue 114](https://github.com/mdn/browser-compat-data/issues/114) for more information.
+We are planning to localize some of this data (for example notes, descriptions). At this point we haven't decided how or when we are going to do that. See [issue 114](https://github.com/mdn/browser-compat-data/issues/114) for more information.

schemas/public.schema.md

@@ -69,8 +69,8 @@ Below is a simplified example of the published data:
 
 The `__meta` object is a required property containing metadata about the published data. It has two required properties:
 
-- `version`: a string containing the package version (e.g. `"6.0.0"`).
-- `timestamp`: a string containing the ISO 8601 date-time when the data was built (e.g. `"2024-01-15T00:00:00.000Z"`).
+- `version`: a string containing the package version (for example `"6.0.0"`).
+- `timestamp`: a string containing the ISO 8601 date-time when the data was built (for example `"2024-01-15T00:00:00.000Z"`).
 
 ### `browsers`
 
@@ -110,14 +110,14 @@ The `__compat` object describes a feature's compatibility data. It consists of t
   In the published data, this property is formatted as HTML.
 
 - An optional `mdn_url` property which **points to an MDN reference page documenting the feature**.
-  It needs to be a valid URL, and should be the language-neutral URL (e.g. use `https://developer.mozilla.org/docs/Web/CSS/text-align` instead of `https://developer.mozilla.org/en-US/docs/Web/CSS/text-align`).
+  It needs to be a valid URL, and should be the language-neutral URL (for example use `https://developer.mozilla.org/docs/Web/CSS/text-align` instead of `https://developer.mozilla.org/en-US/docs/Web/CSS/text-align`).
 
 - An optional `spec_url` property as a URL or an array of URLs, each of which is for a specific part of a specification in which this feature is defined.
   Each URL must contain a fragment identifier.
 
 - An optional `tags` property to assign tags to the feature.
 
-- A mandatory `source_file` property containing the path to the source file that defines this feature, relative to the repository root (e.g. `"api/AbortController.json"`). This is automatically generated at build time.
+- A mandatory `source_file` property containing the path to the source file that defines this feature, relative to the repository root (for example `"api/AbortController.json"`). This is automatically generated at build time.
 
 #### The `support_statement` object