4d
diff --git a/‎docs/API/CollectionClass.md‎
Lines changed: 2 additions & 2 deletions b/‎docs/API/CollectionClass.md‎
Lines changed: 2 additions & 2 deletions
diff --git a/‎docs/Admin/cli.md‎
Lines changed: 1 addition & 1 deletion b/‎docs/Admin/cli.md‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎docs/Admin/dataExplorer.md‎
Lines changed: 3 additions & 3 deletions b/‎docs/Admin/dataExplorer.md‎
Lines changed: 3 additions & 3 deletions
diff --git a/‎docs/Admin/webAdmin.md‎
Lines changed: 1 addition & 1 deletion b/‎docs/Admin/webAdmin.md‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎docs/Concepts/components.md‎
Lines changed: 1 addition & 1 deletion b/‎docs/Concepts/components.md‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎docs/Concepts/error-handling.md‎
Lines changed: 2 additions & 2 deletions b/‎docs/Concepts/error-handling.md‎
Lines changed: 2 additions & 2 deletions
diff --git a/‎docs/Desktop/labels.md‎
Lines changed: 2 additions & 2 deletions b/‎docs/Desktop/labels.md‎
Lines changed: 2 additions & 2 deletions
diff --git a/‎docs/Desktop/sessions.md‎
Lines changed: 1 addition & 1 deletion b/‎docs/Desktop/sessions.md‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎docs/Develop/preemptive.md‎
Lines changed: 1 addition & 1 deletion b/‎docs/Develop/preemptive.md‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎docs/Events/overview.md‎
Lines changed: 1 addition & 1 deletion b/‎docs/Events/overview.md‎
Lines changed: 1 addition & 1 deletion
@@ -2407,11 +2407,11 @@ var $strings1; $strings2 : Collection
 $strings1:=New collection("Alpha";"Charlie";"alpha";"bravo";"Bravo";"charlie")
 
 //using the character code:
-$strings2:=$strings1.orderByMethod(Function(sortCollection);sk character codes)
+$strings2:=$strings1.orderByMethod(Formula(sortCollection);sk char codes)
 // result : ["Alpha","Bravo","Charlie","alpha","bravo","charlie"]
 
 //using the language:
-$strings2:=$strings1.orderByMethod(Function(sortCollection);sk strict)
+$strings2:=$strings1.orderByMethod(Formula(sortCollection);sk strict)
 // result : ["alpha","Alpha","bravo","Bravo","charlie","Charlie"]
 ```
 
 
@@ -45,7 +45,7 @@ Syntax:
 |`--webadmin-settings-file`|File path|Path of the custom WebAdmin `.4DSettings` file for the [WebAdmin web server](webAdmin.md). Not available with [tool4d](#tool4d).|
 |`--webadmin-access-key`|Text|Access key for the [WebAdmin web server](webAdmin.md). Not available with [tool4d](#tool4d).|
 |`--webadmin-auto-start`|Boolean|Status of the automatic startup for the [WebAdmin web server](webAdmin.md). Not available with [tool4d](#tool4d).|
-|`--webadmin-store-settings`||Store the access key and automatic starting parameters in the currently used settings file (i.e. the default [`WebAdmin.4DSettings`](webAdmin.md#webadmin-settings) file or a custom file designated with the `--webadmin-settings-path` parameter). Use the `--webadmin-store-settings` argument to save these settings if necessary. Not available with [tool4d](#tool4d).|
+|`--webadmin-store-settings`||Store the access key and automatic starting parameters in the currently used settings file (i.e. the default [`WebAdmin.4DSettings`](webAdmin.md#settings) file or a custom file designated with the `--webadmin-settings-path` parameter). Use the `--webadmin-store-settings` argument to save these settings if necessary. Not available with [tool4d](#tool4d).|
 |`--utility`||Only available with 4D Server. Launches [4D Server in utility mode](#4d-server-in-utility-mode).|
 |`--skip-onstartup`||Launches the project without executing any "automatic" methods, including the `On Startup` and `On Exit` database methods|
 |`--startup-method`|Project method name (string)|Project method to execute immediately after the `On Startup` database method (if not skipped with `--skip-onstartup`).|
 
@@ -11,14 +11,14 @@ The Data Explorer provides a web interface to view, query, and edit data in your
 
 The Data Explorer relies on the [`WebAdmin`](webAdmin.md) web server component for the configuration and authentication settings.
 
-- **configuration**: the Data Explorer configuration reuses the [`WebAdmin` web server settings](webAdmin.md#webadmin-settings),
-- **authentication**: access to the Data Explorer is granted when the [session user is authenticated](webAdmin.md#authentication-and-session) and has the "WebAdmin" privilege. When the Data Explorer is accessed through the **Data Explorer** menu item (see below), an automatic authentication is provided.
+- **configuration**: the Data Explorer configuration reuses the [`WebAdmin` web server settings](webAdmin.md#settings),
+- **authentication**: access to the Data Explorer is granted when the [session user is authenticated](webAdmin.md#authentication) and has the "WebAdmin" privilege. When the Data Explorer is accessed through the **Data Explorer** menu item (see below), an automatic authentication is provided.
 
 > The Data Explorer access can be disabled using the [`.setAdminProtection()`](API/DataStoreClass.md#setadminprotection) function.
 
 ## Opening the Data Explorer
 
-[The `WebAdmin` web server](webAdmin.md#starting-the-webadmin-web-server) is started automatically if necessary when the Data Explorer is clicked on.
+[The Web Administration Server](webAdmin.md#starting-the-web-administration-server) is started automatically if necessary when the Data Explorer is clicked on.
 
 To connect to the Data Explorer web page:
 
 
@@ -62,7 +62,7 @@ Configuring the Web Administration Server is mandatory in particular to define t
 
 You can configure the Web Administration Server using the [Web Administration settings dialog box](#settings-dialog-box) (see below). 
 
-> If you use a headless 4D application, you can use [*Command Line Interface* arguments](#webadmin-headless-configuration) to define basic settings. You will have to customize the settings file to define advanced parameters. 
+> If you use a headless 4D application, you can use [*Command Line Interface* arguments](#headless-configuration) to define basic settings. You will have to customize the settings file to define advanced parameters. 
 
 
 ### Settings dialog box
 
@@ -31,6 +31,6 @@ You can select a component [project method](methods.md) or [class](classes.md) a
 
 :::note
 
-Interpreted component code can be [edited directly from the host project](../Extensions/develop-components.md#editing-components-from-the-host) if the context is supported. 
+Interpreted component code can be [edited directly from the host project](../Extensions/develop-components.md#creating-and-editing-components-from-the-host) if the context is supported. 
 
 :::
@@ -22,7 +22,7 @@ It is highly recommended to install a global error-handling method on 4D Server,
 :::
 
 
-## Predictable vs unpredictable errors
+## Predictable vs unpredictable errors {#predictable-vs-unpredictable-errors}
 
 Many 4D class functions, such as [`entity.save()`](../API/EntityClass.md#save) or [`transporter.send()`](../API/SMTPTransporterClass.md#send), return a object containing *status* information. This object is used to store **predictable** errors in the runtime context, e.g. invalid password, locked entity, etc., that do not require to stop program execution. This category of errors, also named **silent errors** errors, can be handled by regular code. When such errors occur in an error handling context, i.e. a [`Try`](#tryexpression), [`Try/Catch`](#trycatchend-try) or an [error-handling method](#installing-an-error-handling-method), they do not interrupt the execution and do not trigger the error handling (e.g. the `Catch` part of the [`Try/Catch`](#trycatchend-try) is not executed). They are not listed in the [`Last errors`](../commands/last-errors.md) collection. The error is only returned in the `status` and `statusText` properties of the returned object. It can be processed according to your business logic. 
 
@@ -200,7 +200,7 @@ function test()
 
 ```
 
-3. You want to handle both [predictable and non-predictable](#error-or-status) errors:
+3. You want to handle both [predictable and non-predictable]{#predictable-vs-unpredictable-errors} errors:
 
 ```4d
 var $e:=ds.Employee.new()
 
@@ -147,7 +147,7 @@ The Layout page contains controls for printing labels based on the requirements
 - **Method**: Lets you trigger a specific method that will be run at print time. For example, you can execute a method that posts the date and time that each label was printed. This feature is also useful when you print labels using a dedicated table form, in which case you can fill variables from a method.
 To be eligible for label processing, a project method must comply with the following settings:
   - it must be "allowed" for the database (allowed methods depend on [project settings](../settings/security.md#options) and the [`SET ALLOWED METHODS`](../commands/set-allowed-methods.md) command), otherwise it will not be displayed in the **Apply** menu.
-  - it must have the [Shared by components and host database](../Project/code-overview.md#shared-by-components-and-host-database) option.
+  - it must have the [Shared by components and host database](../Project/project-method-properties.md#shared-by-components-and-host-database) option.
 See also [this example](#printing-labels-using-forms-and-methods-example) below.
 
 :::note 
@@ -178,7 +178,7 @@ Here, in a table form named "label", we added the *myVar* variable:
  var myVar+=1
 ```
 
-3. Set the project method as ["Shared by components and host database"](../Project/code-overview.md#shared-by-components-and-host-database).
+3. Set the project method as ["Shared by components and host database"](../Project/project-method-properties.md#shared-by-components-and-host-database).
 
 4. Before displaying the Label editor, make sure the project method is allowed by executing this code:
 
 
@@ -65,7 +65,7 @@ You can also assign privileges to a remote user session to control access when t
 
 The remote user `session` object is available from:
 
-- Project methods that have the [Execute on Server](../Project/code-overview.md#execute-on-server) attribute (they are executed in the "twinned" process of the client process),
+- Project methods that have the [Execute on Server](../Project/project-method-properties.md#execute-on-server) attribute (they are executed in the "twinned" process of the client process),
 - Triggers,
 - ORDA [data model functions](../ORDA/ordaClasses.md) (except those declared with the [`local`](../ORDA/ordaClasses.md#local-functions) keyword), 
 - Database methods such as [`On Server Open Connection`](../commands/on-server-open-connection-database-method) and [`On Server Close Connection`](../commands/on-server-close-connection-database-method).
 
@@ -79,7 +79,7 @@ Note that with this option, whatever the internal thread safety evaluation, the
 
 :::note Particular case
 
-If the method has also the [**Shared by components and host database**](../Project/code-overview.md#shared-by-components-and-host-database) property, setting the **Indifferent** option will automatically tag the method as thread-unsafe. If you want a shared component method to be thread-safe, you must explicitely set it to **Can be run in preemptive processes**.
+If the method has also the [**Shared by components and host database**](../Project/project-method-properties.md#shared-by-components-and-host-database) property, setting the **Indifferent** option will automatically tag the method as thread-unsafe. If you want a shared component method to be thread-safe, you must explicitely set it to **Can be run in preemptive processes**.
 
 :::
 
 
@@ -29,7 +29,7 @@ objectName|text|Name of the object triggering the event - Not included if the ev
 
 Additional properties are returned when the event occurs on specific objects. In particular:
 
-- [list boxes](FormObjects/listbox_overview.md#supported-form-events) and [list box columns](FormObjects/listbox_overview.md#supported-form-events-1) return [additional properties](FormObjects/listbox_overview.md#additional-properties) such as `columnName` or `isRowSelected`.
+- [list boxes](FormObjects/listbox_overview.md#supported-form-events) and [list box columns](FormObjects/listbox_overview.md#supported-form-events-1) return [additional properties](FormObjects/listbox_overview.md#supported-form-events) such as `columnName` or `isRowSelected`.
 - [4D View Pro areas](FormObjects/viewProArea_overview.md) return for example `sheetName` or `action` properties in the [On After Edit](onAfterEdit.md) event object.