Docs: more consistent naming

Author: jackocnr

site/src/docs/markdown/best_practices.md

@@ -24,11 +24,11 @@ _<sup>*</sup>Except for some small satellite territories, which share number ran
 
 ## Validate before saving
 
-Check the number is valid before storing it, and reject invalid input. Get the validity from [`isValidNumber`](/docs/methods#isvalidnumber) (core library) or the `onChangeValidity` / `validityChange` callback (components). Requires the utils module.
+Check the number is valid before storing it, and reject invalid input. Get the validity from [`isValidNumber`](/docs/methods#isvalidnumber) (vanilla JS library) or the `onChangeValidity` / `validityChange` callback (framework components). Requires the utils module.
 
 ##### Deriving a user-facing error message
 
-When a number is invalid, you'll get an error code (from [`getValidationError`](/docs/methods#getvalidationerror) for the core library, or via the `onChangeErrorCode` / `errorCodeChange` callback for the components). Mapping the error codes to user-facing messages is left to you because the wording belongs to your app. Here is a reasonable starting point:
+When a number is invalid, you'll get an error code (from [`getValidationError`](/docs/methods#getvalidationerror) for the vanilla JS library, or via the `onChangeErrorCode` / `errorCodeChange` callback for the framework components). Mapping the error codes to user-facing messages is left to you because the wording belongs to your app. Here is a reasonable starting point:
 
 ```js
 const getErrorMessage = (number, errorCode) => {
@@ -47,7 +47,7 @@ const getErrorMessage = (number, errorCode) => {
 
 ## Keep strict mode on, with rejection feedback
 
-[`strictMode`](/docs/options#strictmode) is on by default and rejects non-numeric characters while capping the length at the country's max as the user types. Just as importantly, the rejection shouldn't be silent — by default, [`strictRejectAnimation`](/docs/options#strictrejectanimation) plays a built-in shake/flash animation so the user notices. For richer feedback (e.g. a toast that explains _why_ the input was rejected), listen for the `strict:reject` event (core library) or use the equivalent `onStrictReject` / `strictReject` callback (components).
+[`strictMode`](/docs/options#strictmode) is on by default and rejects non-numeric characters while capping the length at the country's max as the user types. Just as importantly, the rejection shouldn't be silent — by default, [`strictRejectAnimation`](/docs/options#strictrejectanimation) plays a built-in shake/flash animation so the user notices. For richer feedback (e.g. a toast that explains _why_ the input was rejected), listen for the `strict:reject` event (vanilla JS library) or use the equivalent `onStrictReject` / `strictReject` callback (framework components).
 
 ## Set the initial country
 

site/src/docs/markdown/integrations.md

@@ -2,7 +2,7 @@
 
 ## Choose your integration
 
-`intl-tel-input` comes in two flavours: a **vanilla JavaScript library** and a set of native **framework components**. Both offer the same core features — country picker, formatting and validation — so pick the one that matches your stack.
+`intl-tel-input` comes in two flavours: a **vanilla JavaScript library** and a set of native **framework components**. Both offer the same core features — country picker, formatting and validation — so pick the one that matches your stack. Internally, both are powered by the same shared engine (referred to throughout these docs as the **core library**) — the vanilla JS library exposes it directly, while the framework components wrap it.
 
 <div class="iti-integration-choice row g-4 my-4">
   <div class="col-md-6">
@@ -49,7 +49,7 @@ Technically yes, but our native framework components are the recommended path -
 * **Lifecycle handled** — initialisation on mount and `destroy()` on unmount, so you don't leak instances or listeners.
 * **Two-way value binding** — pass the number in as a prop and it stays in sync with your app's state, with internal guards to avoid cursor jumps while typing.
 * **Typed change callbacks** — `changeNumber`, `changeCountry`, `changeValidity`, and `changeErrorCode` exposed as idiomatic, fully-typed handlers for each framework.
-* **Escape hatch** — grab the underlying core library instance via a ref for anything the component doesn't expose directly.
+* **Escape hatch** — grab the core library instance via a ref for anything the component doesn't expose directly.
 
 **Do the components include all the core library features?**  
 Yes — plus more. All [initialisation options](/docs/options) and [methods](/docs/methods) are available through the component props and refs, and on top of that you get the framework-native conveniences like two-way binding and typed callbacks (see above).

site/src/docs/markdown/methods.md

@@ -122,7 +122,7 @@ Type: `() => boolean`
 
 ⚠️ **ADVANCED**  
 (Note: only returns `true` for valid **mobile** and **fixed_line** numbers by default - see [`allowedNumberTypes`](/docs/options#allowednumbertypes))  
-Check if the current number is valid using precise matching rules for each country/area code, etc - [see example](/examples/vanilla-javascript/validation-precise). Note that these rules change each month for various countries around the world, so you need to constantly keep the core library up-to-date (e.g. via an automated script) else **you will start rejecting valid numbers**. For a simpler and more future-proof form of validation, see [`isValidNumber`](/docs/methods#isvalidnumber) above. If validation fails, you can use [`getValidationError`](/docs/methods#getvalidationerror) to get more information. Requires the [utils script to be loaded](/docs/utils#loading-the-utils-script).  
+Check if the current number is valid using precise matching rules for each country/area code, etc - [see example](/examples/vanilla-javascript/validation-precise). Note that these rules change each month for various countries around the world, so you need to constantly keep the package up-to-date (e.g. via an automated script) else **you will start rejecting valid numbers**. For a simpler and more future-proof form of validation, see [`isValidNumber`](/docs/methods#isvalidnumber) above. If validation fails, you can use [`getValidationError`](/docs/methods#getvalidationerror) to get more information. Requires the [utils script to be loaded](/docs/utils#loading-the-utils-script).  
 
 ```js
 const isValid = iti.isValidNumberPrecise();

site/src/docs/markdown/utils.md

@@ -17,7 +17,7 @@ The utils script adds ~260KB on top of the ~30KB core library. There are two way
 Use the [`loadUtils`](/docs/options#loadutils) option to fetch the utils separately. The core library/component loads quickly (~30KB); the ~260KB utils file is fetched in the background after initialisation, so formatting/validation kicks in shortly after the input appears without blocking your initial page load.
 
 **Option 2: Use the all-in-one bundle**  
-Each distribution ships a companion entry point that bundles utils directly — `intl-tel-input/intlTelInputWithUtils` for the vanilla JavaScript library, `@intl-tel-input/react/with-utils` for React, `@intl-tel-input/vue/with-utils` for Vue, and so on. Everything works out of the box, with no extra configuration. Best if you're already lazy loading the main script, or if the extra ~260KB up front isn't a concern.
+Each distribution ships a companion entry point that bundles utils directly — `intl-tel-input/intlTelInputWithUtils` for the vanilla JavaScript library, `@intl-tel-input/react/with-utils` for React, `@intl-tel-input/vue/with-utils` for Vue, and so on. Everything works out of the box, with no extra configuration. Best if you're already lazy loading the core library, or if the extra ~260KB up front isn't a concern.
 
 For exact code, see the quick-start on the relevant docs page: [vanilla JavaScript library](/docs/vanilla-javascript), [React](/docs/react-component), [Vue](/docs/vue-component), [Angular](/docs/angular-component), or [Svelte](/docs/svelte-component).
 

site/src/docs/markdown/vanilla_javascript.md

@@ -13,7 +13,7 @@ How to get up and running with the vanilla JavaScript library. See a live demo o
 
 ## Installation
 
-There are two ways to install the core library: [using a bundler](#using-a-bundler) (e.g. Vite, webpack), or [using a script tag](#using-a-script-tag) (e.g. via a CDN).
+There are two ways to install the library: [using a bundler](#using-a-bundler) (e.g. Vite, webpack), or [using a script tag](#using-a-script-tag) (e.g. via a CDN).
 
 ##### Using a bundler
 
@@ -23,7 +23,7 @@ First, install the package:
 npm install intl-tel-input
 ```
 
-Then, import the JS and CSS, and initialise the core library on your input element:
+Then, import the JS and CSS, and initialise it on your input element:
 
 ```js
 import intlTelInput from "intl-tel-input";
@@ -36,7 +36,7 @@ intlTelInput(input, {
 ```
 
 > [!NOTE]
-> The utils script (~260KB) is loaded separately. The example above passes a dynamic import to [`loadUtils`](/docs/options#loadutils) — modern bundlers split this into its own lazy-loaded chunk, so it doesn't hit your initial bundle. Alternatively, if the core library is already lazy-loaded in your app, import from `"intl-tel-input/intlTelInputWithUtils"` to bundle utils directly.
+> The utils script (~260KB) is loaded separately. The example above passes a dynamic import to [`loadUtils`](/docs/options#loadutils) — modern bundlers split this into its own lazy-loaded chunk, so it doesn't hit your initial bundle. Alternatively, if the library is already lazy-loaded in your app, import from `"intl-tel-input/intlTelInputWithUtils"` to bundle utils directly.
 
 ##### Using a script tag
 
@@ -48,7 +48,7 @@ First, add the CSS:
 <link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/intl-tel-input@27.1.3/dist/css/intlTelInput.css">
 ```
 
-Then, add the core library script and initialise it on your input element:
+Then, add the script and initialise it on your input element:
 
 ```html
 <script src="https://cdn.jsdelivr.net/npm/intl-tel-input@27.1.3/dist/js/intlTelInput.min.js"></script>
@@ -68,17 +68,17 @@ See [Best practices](/docs/best-practices) for general advice on loading the uti
 
 ## Initialisation options
 
-The core library has dozens of options for customising its behaviour — country picker, formatting, validation, placeholders, localisation, and more. See the full list on the [Initialisation options](/docs/options) page, or try them interactively in the [playground](/playground).
+The library has dozens of options for customising its behaviour — country picker, formatting, validation, placeholders, localisation, and more. See the full list on the [Initialisation options](/docs/options) page, or try them interactively in the [playground](/playground).
 
 
 ## Methods
 
-Once the core library is initialised, you can call methods on the returned instance — e.g. `setNumber`, `setCountry`, `getNumber`, `isValidNumber`. See the full list on the [Methods](/docs/methods) page.
+Once initialised, you can call methods on the returned instance — e.g. `setNumber`, `setCountry`, `getNumber`, `isValidNumber`. See the full list on the [Methods](/docs/methods) page.
 
 
 ## Events
 
-The core library triggers the following custom events on the `<input>` element. Listen for them with `input.addEventListener(...)`.
+The library triggers the following custom events on the `<input>` element. Listen for them with `input.addEventListener(...)`.
 
 ##### countrychange