Standardize "lower case" and "upper case" to "lowercase" and "uppercase" across documentation

dataminer/Functions/DOM/DOM_DevOps/DOM_Editor/DOM_editor_new_def.md

@@ -12,7 +12,7 @@ uid: DOM_editor_new_def
 
    ![DOM Editor starting window](~/dataminer/images/DOM_Editor_new.png)
 
-1. In the *Module ID* box, specify the name of the module you want to add. The name must be in lower case only.
+1. In the *Module ID* box, specify the name of the module you want to add. The name must be in lowercase only.
 
    ![DOM Editor: new module window](~/dataminer/images/DOM_Editor_new2.png)
 

dataminer/Functions/DOM/DOM_actions.md

@@ -183,7 +183,7 @@ The `DomInstanceButtonDefinition` has the following properties:
 
 | Name | Type | Description |
 |--|--|--|
-| Id | string | The ID of the button. This must be unique to this `DomBehaviorDefinition` and must be lower case. |
+| Id | string | The ID of the button. This must be unique to this `DomBehaviorDefinition` and must be lowercase. |
 | Layout | DomButtonDefinitionLayout | Contains extra properties to define how the button will be displayed (see properties table below). |
 | VisibilityCondition | IDomInstanceCondition | Condition that defines when the button will be shown. |
 | ActionDefinitionIds | List\<string> | Contains the ID of the action that should be executed. Can contain multiple, but currently, only one is allowed. |

dataminer/Troubleshooting/Known_issues/KI_Inaccessible_data_Elasticsearch_casing.md

@@ -11,7 +11,7 @@ uid: KI_Inaccessible_data_Elasticsearch_casing
 
 ## Cause
 
-If a logger table that has `Indexing` set to `true` contains column names with uppercase characters, SLDataGateway incorrectly changes these column names to lower case. This leads to the data getting stored in a different field than expected and therefore not being retrieved when requested.
+If a logger table that has `Indexing` set to `true` contains column names with uppercase characters, SLDataGateway incorrectly changes these column names to lowercase. This leads to the data getting stored in a different field than expected and therefore not being retrieved when requested.
 
 ## Fix
 

develop/devguide/Visio/linking_shapes/Linking_a_shape_to_a_webpage.md

@@ -95,7 +95,7 @@ If you want to pass on the user credentials of the current user to a webpage dis
 
 ## Allowing pop-ups
 
-In DataMiner Cube, embedded browser windows suppress pop-ups by default. If, for any reason, you want an embedded browser window to allow pop-ups (e.g. when it has to show an authentication dialog), then you can use the following URL suffix (in upper case):
+In DataMiner Cube, embedded browser windows suppress pop-ups by default. If, for any reason, you want an embedded browser window to allow pop-ups (e.g. when it has to show an authentication dialog), then you can use the following URL suffix (in uppercase):
 
 ```txt
 #SL_ALLOW_POPUPS#

develop/devguide/Visio/reference/Visio_styleguide.md

@@ -82,7 +82,7 @@ Default font: Segoe UI​
 
 ### Casing
 
-#### Upper case​ (i.e. all letters of all words are capitalized​)
+#### Uppercase​ (i.e. all letters of all words are capitalized​)
 
 - Titles​
 - Buttons​

develop/schemadoc/Protocol/EnumParamMeasurementTypeCase.md

@@ -11,5 +11,5 @@ Specifies the casing type.
 |Item|Facet value|Description|
 |--- |--- |--- |
 |***string restriction***|||
-|  Enumeration|lower|Lower case|
-|  Enumeration|upper|Upper case|
+|  Enumeration|lower|Lowercase|
+|  Enumeration|upper|Uppercase|

release-notes/Cloud/dataminer_services_change_log_2024_07to12.md

@@ -336,7 +336,7 @@ Previously, when a Catalog item had a public range but private versions, it coul
 
 #### 23 September 2024 - Enhancement - Catalog API - Enhanced image path format support when registering Catalog item [ID 40862]
 
-When you register a Catalog item with a readme.md file, in that file you can now reference to an image using the home directory path "~" syntax or using a relative path. In addition, the casing of the image directory mentioned in the markdown file no longer matters, while previously this always had to be lower case.
+When you register a Catalog item with a readme.md file, in that file you can now reference to an image using the home directory path "~" syntax or using a relative path. In addition, the casing of the image directory mentioned in the markdown file no longer matters, while previously this always had to be lowercase.
 
 #### 23 September 2024 - Fix - Catalog - Duplicate Catalog items [ID 40839]
 

release-notes/DIS/DIS_2.8.md

@@ -90,7 +90,7 @@ In some cases, the display editor would reset the default page when that page di
 
 #### IDE - Table editor: Column options no longer converted to lowercase \[ID 17313\]
 
-In some cases, dynamic items defined in \<ColumnOption> tags would incorrectly be converted to lower case when you applied changes made in the table editor. An options attribute like `;save;SelectionSetVar:VariableName` would, for example, get converted to `;save;SelectionSetVar:variablename`. This problem has now been fixed.
+In some cases, dynamic items defined in \<ColumnOption> tags would incorrectly be converted to lowercase when you applied changes made in the table editor. An options attribute like `;save;SelectionSetVar:VariableName` would, for example, get converted to `;save;SelectionSetVar:variablename`. This problem has now been fixed.
 
 #### Validator: Problem when a column parameter could not be found \[ID 17394\]
 

release-notes/General/General_Feature_Release_10.0/General_Feature_Release_10.0.3.md

@@ -537,9 +537,9 @@ When you created a new element, service, view or redundancy group, in some cases
 
 In some rare cases, it would not be possible to click DCF connection lines when a placeholder was specified in the *Connection* shape. Also, connection lines would no longer become transparent when hovering the mouse pointer over them.
 
-#### Module names in SLErrors.txt in upper case \[ID 24626\]
+#### Module names in SLErrors.txt in uppercase \[ID 24626\]
 
-In some cases, it could occur that the DataMiner module names in the SLErrors.txt log file were listed in upper case.
+In some cases, it could occur that the DataMiner module names in the SLErrors.txt log file were listed in uppercase.
 
 #### Problem during protocol buffer serialization \[ID 24630\]
 

release-notes/General/General_Feature_Release_10.2/General_Feature_Release_10.2.10.md

@@ -260,7 +260,7 @@ In the user settings (*user icon > Settings*), from now on, you will only be abl
 
 A number of small enhancements have been made to the header bar of low-code apps:
 
-- Button text now supports both upper case and lower case.
+- Button text now supports both uppercase and lowercase.
 - Buttons no longer have lines between them.
 
 #### Enhanced performance when starting up elements on systems using a MySQL or Microsoft SQL Server database [ID 34265]

release-notes/General/General_Feature_Release_10.3/General_Feature_Release_10.3.6.md

@@ -390,6 +390,6 @@ In some cases, whitespace characters would incorrectly be removed from signature
 
 <!-- MR 10.3.0 [CU3] - FR 10.3.6 [CU0] -->
 
-Since DataMiner versions 10.3.0/10.3.3, if a logger table that had `Indexing` set to true contained column names with uppercase characters, *SLDataGateway* would incorrectly change these column names to lower case. This lead to the data getting stored in a different field than expected and therefore not being retrieved when requested.
+Since DataMiner versions 10.3.0/10.3.3, if a logger table that had `Indexing` set to true contained column names with uppercase characters, *SLDataGateway* would incorrectly change these column names to lowercase. This lead to the data getting stored in a different field than expected and therefore not being retrieved when requested.
 
 For more information on this issue, see [Inaccessible logger table data in Elasticsearch because of incorrect casing](xref:KI_Inaccessible_data_Elasticsearch_casing)

release-notes/General/General_Main_Release_10.0/General_Main_Release_10.0.0_fixes_1.md

@@ -464,7 +464,7 @@ A number of issues have been resolved that could occur with the breadcrumbs at t
 - When an object was renamed, it could occur that the name in the breadcrumbs was not updated.
 - When an object had been deleted, it could occur that it was still displayed in the breadcrumbs' dropdown menu.
 - For services that only contained excluded devices, it could occur that breadcrumbs were not displayed correctly.
-- Breadcrumbs will no longer be displayed in upper case only.
+- Breadcrumbs will no longer be displayed in uppercase only.
 
 In addition, on a view card, it could occur that the list of elements was not updated if an element was removed from the view while the card was open.
 

release-notes/General/General_Main_Release_10.2/General_Main_Release_10.2.0_CU7.md

@@ -130,7 +130,7 @@ In the user settings (*user icon > Settings*), from now on, you will only be abl
 
 A number of small enhancements have been made to the header bar of Low-Code Apps:
 
-- Button text now supports both upper case and lower case.
+- Button text now supports both uppercase and lowercase.
 - Buttons no longer have lines between them.
 
 #### Enhanced performance when starting up elements on systems using a MySQL or Microsoft SQL Server database [ID 34265]

release-notes/General/General_Main_Release_10.3/General_Main_Release_10.3.0_CU3.md

@@ -285,6 +285,6 @@ When an element that had more than 10,000 alarm events stored on a Cassandra clu
 
 <!-- MR 10.3.0 [CU3] - FR 10.3.6 [CU0] -->
 
-Since DataMiner versions 10.3.0/10.3.3, if a logger table that had `Indexing` set to true contained column names with uppercase characters, *SLDataGateway* would incorrectly change these column names to lower case. This lead to the data getting stored in a different field than expected and therefore not being retrieved when requested.
+Since DataMiner versions 10.3.0/10.3.3, if a logger table that had `Indexing` set to true contained column names with uppercase characters, *SLDataGateway* would incorrectly change these column names to lowercase. This lead to the data getting stored in a different field than expected and therefore not being retrieved when requested.
 
 For more information on this issue, see [Inaccessible logger table data in Elasticsearch because of incorrect casing](xref:KI_Inaccessible_data_Elasticsearch_casing)

release-notes/Web_apps/Web_apps_Feature_Release_10.3/Web_apps_Feature_Release_10.3.10.md

@@ -213,11 +213,11 @@ When you enabled the *Show seconds* option of multiple clock components on the s
 
 Up to now, when you edited a published app that had a draft, a new draft would incorrectly be created. From now on, when you edit an app that has a draft, that existing draft will be opened.
 
-#### Dashboards app/Low-Code Apps: Label of 'Icon' setting of 'Icon' component would incorrectly be in lower case [ID 37199]
+#### Dashboards app/Low-Code Apps: Label of 'Icon' setting of 'Icon' component would incorrectly be in lowercase [ID 37199]
 
 <!-- MR 10.4.0 - FR 10.3.10 -->
 
-The label of the *Icon* setting of an *Icon* component would incorrectly be in lower case. It is now in upper case.
+The label of the *Icon* setting of an *Icon* component would incorrectly be in lowercase. It is now in uppercase.
 
 #### Low-Code Apps: Problem when two State components were fed the same query row data with a column filter applied [ID 37206]