Spelling/grammar corrections UI

dataminer/Administrator_guide/Failover/Configuring_Failover/Advanced_Failover_options.md

@@ -64,4 +64,4 @@ This tab is not available if a shared hostname is used instead of virtual IP add
 
 This tab is available from DataMiner 10.2.0 \[CU5]/10.2.8 onwards. It contains the following option:
 
-- **Auto restart Agent when going offline**: If you select this option, when one of the DMAs in the Failover pair goes offline, it will restart as soon as possible instead of waiting until all elements have been unloaded. This will speed up Failover switching. In earlier DataMiner versions, this could be configured in [DMS.xml](xref:DMS_xml#failover-subtag).
+- **Auto-restart Agent when going offline**: If you select this option, when one of the DMAs in the Failover pair goes offline, it will restart as soon as possible instead of waiting until all elements have been unloaded. This will speed up Failover switching. In earlier DataMiner versions, this could be configured in [DMS.xml](xref:DMS_xml#failover-subtag).

dataminer/Functions/Correlation/Adding_rule_actions/Escalating_an_event.md

@@ -21,4 +21,4 @@ To configure this, in the *Actions* section of the details pane:
 
 1. Click *Add Action* and select *Escalate event*.
 
-1. Optionally, to also clear the escalated correlated alarm when the conditions are no longer fulfilled, select *Auto clear*.
+1. Optionally, to also clear the escalated correlated alarm when the conditions are no longer fulfilled, select *Autoclear*.

dataminer/Functions/Correlation/Adding_rule_actions/Triggering_a_correlated_alarm.md

@@ -31,7 +31,7 @@ To make a Correlation rule trigger a new, correlated alarm:
 
 1. If necessary, select one or more of the following options:
 
-   - **Auto clear**: Select this option if you want the Correlation alarm to be cleared automatically as soon as the conditions specified in the Correlation rule are no longer met.
+   - **Autoclear**: Select this option if you want the Correlation alarm to be cleared automatically as soon as the conditions specified in the Correlation rule are no longer met.
 
    - **Include name in alarm value**: Select this option if you want the name of the Correlation rule to be included in the alarm value.
 

dataminer/Functions/DataMiner_Assistant/DataMiner_Assistant.md

@@ -29,6 +29,6 @@ For example, you will be able to ask which alarms require immediate attention, a
 
 In the *Documentation* tab, the Assistant will focus on conceptual and procedural questions. It will have direct access to DataMiner Docs, allowing it to provide accurate and up-to-date information directly from the source.
 
-You will be able to ask questions such as which low-code app visualization type is best for large data sets, how to configure an alarm template, or how DataMiner user permissions work. The Assistant will then retrieve the relevant information for you, allowing you to find documentation content quickly without needing to browse through the DataMiner documentation manually.
+You will be able to ask questions such as which low-code app visualization type is best for large datasets, how to configure an alarm template, or how DataMiner user permissions work. The Assistant will then retrieve the relevant information for you, allowing you to find documentation content quickly without needing to browse through the DataMiner documentation manually.
 
 ![Documentation tab](~/dataminer/images/Assistant_Documentation_tab.png)

dataminer/Functions/Router_Control/Creating_and_customizing_RC_configs/Overview_of_user_interface_component_properties.md

@@ -33,7 +33,7 @@ None
 | Name | The text of the label. |
 | TextAlignment | The alignment of the text: Left, Right, Center, or Justify. |
 | TextWrapping  | Whether or not text will wrap when it reaches the edge of the label box:<br> -  Wrap: Text will always wrap when it reaches the edge of the label box.<br> -  WrapWithOverflow: Text will always wrap when it reaches the edge of the label box, except in case of long words.<br> -  NoWrap: No line wrapping is performed.              |
-| TextTrimming  | The way in which text is trimmed when it overflows the edge of the label box.<br> -  None: Text is not trimmed.<br> -  CharacterEllipsis: Text is trimmed after a character. An ellipsis (”...”) will replace the remaining text.<br> -  WordEllipsis: Text is trimmed after a word. An ellipsis (”...”) will replace the remaining text. |
+| TextTrimming  | The way text is trimmed when it overflows the edge of the label box.<br> -  None: Text is not trimmed.<br> -  CharacterEllipsis: Text is trimmed after a character. An ellipsis (”...”) will replace the remaining text.<br> -  WordEllipsis: Text is trimmed after a word. An ellipsis (”...”) will replace the remaining text. |
 | FontFamily | The text font. |
 | FontSize | The text font size (in points). |
 | FontWeight | The font weight: Normal, Bold, or Light |

dataminer/Operator_guide/Services/Service_templates/Creating_a_service_template/ST_specifying_general_characteristics.md

@@ -14,7 +14,7 @@ In addition, two advanced options are available in the *General* tab:
 
 - Select *Require confirmation before applying* to ensure that the user has to confirm before the service template is applied.
 
-- Select *Auto execute template when new elements have been added in the system* to automatically apply the service template when a new element is added in the DMS.
+- Select *Auto-execute template when new elements have been added in the system* to automatically apply the service template when a new element is added in the DMS.
 
 > [!NOTE]
 > If the service template is automatically applied when a new element is added, the *Background Tasks* window will appear so that you can follow the progress.

develop/TOOLS/DIS/Editors/C_editor.md

@@ -35,7 +35,7 @@ If you right-click anywhere in the editor and select the *Copy Protocol to Clipb
 
 If you right-click anywhere in the editor and select the *Copy Code to Clipboard* command, the entire content of the file will be copied to the Windows Clipboard.
 
-When you use this menu option while working with a protocol solution or an Automation script solution, you will not only copy the current file to the Windows clipboard, but all files of the entire project combined in a way that is similar to the way in which they are combined when the solution is compiled.
+When you use this menu option while working with a protocol solution or an Automation script solution, you will not only copy the current file to the Windows clipboard, but all files of the entire project combined in a way that is similar to the way they are combined when the solution is compiled.
 
 ### Repeating selected text
 

develop/TOOLS/DIS/Editors/Display_editor.md

@@ -15,7 +15,7 @@ If you click *Display Editor* in the file tab header when editing a protocol XML
 
 On the left, you can find the list of existing pages.
 
-This section visualizes data pages and pop-up windows in a tree view, similar to the way in which they are displayed in DataMiner Cube. Pop-up windows are shown as child items of the data pages in which they are defined.
+This section visualizes data pages and pop-up windows in a tree view, similar to the way they are displayed in DataMiner Cube. Pop-up windows are shown as child items of the data pages in which they are defined.
 
 > [!NOTE]
 > Warning icons will appear next to pages that are empty and pop-up windows in which other pop-up windows are defined.

develop/devguide/Connector/ConnectionsWebSocketsCommunication.md

@@ -4,7 +4,7 @@ uid: ConnectionsWebSocketsCommunication
 
 # Communication
 
-Once the WebSocket has been set up, data can be sent and received. Commands are implemented using *Command* constructs, and Responses can be implemented using *Response* constructs. This is identical to the way in which serial connections work.
+Once the WebSocket has been set up, data can be sent and received. Commands are implemented using *Command* constructs, and Responses can be implemented using *Response* constructs. This is identical to the way serial connections work.
 
 For traditional request/response communication, a command and response can be combined in a pair. Similar to HTTP, when a response is not received, the connection will time out.
 

develop/schemadoc/Protocol/Protocol.Params.Param.Measurement.Type-options.md

@@ -270,7 +270,7 @@ With this option, you can set the properties of the table (separated by commas).
 - **columns**: The order of the column parameters.
 - **lines**: The number of lines.
 - **width**: The width of each column (in pixels).
-- **sort**: The way in which columns are interpreted for sorting. You can add a sort order and a priority.
+- **sort**: The way columns are interpreted for sorting. You can add a sort order and a priority.
 
   Example:
 

release-notes/General/General_Feature_Release_10.6/General_Feature_Release_10.6.1.md

@@ -435,11 +435,11 @@ Up to now, when DVE elements were deleted while multiple DVE elements were havin
 
 When a QAction triggered an information message with regard to a particular element, SLNet would incorrectly only forward that message to the DataMiner Agent that hosted that element. As a result, that information message would not appear in client applications connected to any of the other DataMiner Agents in the system.
 
-#### Correlation alarms triggered by a correlation rule with the 'Auto clear' option set would not be cleared automatically [ID 43974]
+#### Correlation alarms triggered by a correlation rule with the 'Autoclear' option set would not be cleared automatically [ID 43974]
 
 <!-- MR 10.6.0 - FR 10.6.1 -->
 
-When, in a correlation rule, a *New alarm* or an *Escalate event* action was configured with the *Auto clear* option set, in some cases, the new correlated alarms triggered by that correlation rule would incorrectly not be automatically cleared.
+When, in a correlation rule, a *New alarm* or an *Escalate event* action was configured with the *Autoclear* option set, in some cases, the new correlated alarms triggered by that correlation rule would incorrectly not be automatically cleared.
 
 #### Element and parameter state timelines could show incorrect data [ID 43982]
 

release-notes/General/General_Feature_Release_10.6/General_Feature_Release_10.6.2.md

@@ -107,7 +107,7 @@ If the DataMiner System is a STaaS system, adding a DataMiner Agent will also fa
 
 <!-- MR 10.5.0 [CU11] - FR 10.6.2 -->
 
-When, on a system with a Cassandra Cluster database, history alarms are filtered on service ID or service name, up to now, that filter would not be translated correctly to Elasticsearch or OpenSearch. From now on, that filter will be translated correctly. As a result, overall performance will increase when applying the filter in question to large data sets.
+When, on a system with a Cassandra Cluster database, history alarms are filtered on service ID or service name, up to now, that filter would not be translated correctly to Elasticsearch or OpenSearch. From now on, that filter will be translated correctly. As a result, overall performance will increase when applying the filter in question to large datasets.
 
 Also, filtering on alarm properties or interfaces using wildcards or regular expression has now been made case insensitive.
 

release-notes/General/General_Main_Release_10.5/General_Main_Release_10.5.0_CU11.md

@@ -47,7 +47,7 @@ Note that, from now on, if not all nodes of the OpenSearch cluster are listed in
 
 <!-- MR 10.5.0 [CU11] - FR 10.6.2 -->
 
-When, on a system with a Cassandra Cluster database, history alarms are filtered on service ID or service name, up to now, that filter would not be translated correctly to Elasticsearch or OpenSearch. From now on, that filter will be translated correctly. As a result, overall performance will increase when applying the filter in question to large data sets.
+When, on a system with a Cassandra Cluster database, history alarms are filtered on service ID or service name, up to now, that filter would not be translated correctly to Elasticsearch or OpenSearch. From now on, that filter will be translated correctly. As a result, overall performance will increase when applying the filter in question to large datasets.
 
 Also, filtering on alarm properties or interfaces using wildcards or regular expression has now been made case insensitive.
 

release-notes/General/General_Main_Release_10.6/General_Main_Release_10.6.0_changes.md

@@ -754,11 +754,11 @@ From now on, when you try to install Alerter, it will check whether Microsoft .N
 
 Up to now, because of SLNet caching issues, in client applications like e.g. DataMiner Cube, outdated SLAnalytics icons would incorrectly remain visible for too long.
 
-#### Correlation alarms triggered by a correlation rule with the 'Auto clear' option set would not be cleared automatically [ID 43974]
+#### Correlation alarms triggered by a correlation rule with the 'Autoclear' option set would not be cleared automatically [ID 43974]
 
 <!-- MR 10.6.0 - FR 10.6.1 -->
 
-When, in a correlation rule, a *New alarm* or an *Escalate event* action was configured with the *Auto clear* option set, in some cases, the new correlated alarms triggered by that correlation rule would incorrectly not be automatically cleared.
+When, in a correlation rule, a *New alarm* or an *Escalate event* action was configured with the *Autoclear* option set, in some cases, the new correlated alarms triggered by that correlation rule would incorrectly not be automatically cleared.
 
 #### DataMiner backup would fail with an incorrect Elasticsearch error due to a Db.xml parsing issue [ID 44044]