Merge branch 'main' into blockly_http

configuration/jsr223.md

@@ -369,7 +369,7 @@ scriptExtension.importPreset("RuleSupport")
 | ModuleBuilder     | `org.openhab.core.automation.ModuleBuilder`                                       |
 | Rule              | `org.openhab.core.automation.Rule` (use `SimpleRule` for defining rules)          |
 | Trigger           | `org.openhab.core.automation.Trigger`                                             |
-| TriggerBuilder    | `org.openhab.core.automation.TriggerBuilder`                                      |
+| TriggerBuilder    | `org.openhab.core.automation.util.TriggerBuilder`                                 |
 | automationManager | Instance for managing rules and other openHAB module instances. (e.g., `addRule`) |
 | ruleRegistry      | `org.openhab.core.automation.Rule`                                                |
 

configuration/transformations.md

@@ -40,8 +40,7 @@ Transformation files need to be placed in the directory `$OPENHAB_CONF/transform
     ```
 
     Usage of Transformations in the [label parameter of Sitemap elements]({{base}}/ui/sitemaps.html#element-type-text) works the same way.
-
-2. Rules
+1. Rules
 
     Transformations can also be [used in rules]({{base}}/configuration/rules-dsl.html#transformations) to transform/translate/convert data.
     The following shows three examples:
@@ -52,12 +51,12 @@ Transformation files need to be placed in the directory `$OPENHAB_CONF/transform
     var fahrenheit = transform("JS", "convert-C-to-F.js", temperature)
     ```
 
-3. Bindings
+1. Bindings
 
     Transformations can sometimes be used in binding add-ons.  For example, transforming an openHAB ON command into "action=powerup" for sending to a device.
     If, and how, this use may be available is described in individual binding documentation.
 
-4. Profiles
+1. Profiles
 
     Transformations can be associated with channels, working on data being passed between bindings and Items. See [profile documentation]({{base}}/configuration/items.html#profiles) for more detail.
 

tutorials/getting_started/custom_widgets.md

@@ -195,7 +195,7 @@ Up to this point the tutorial has focused on list item widgets because as someon
 However, there is that Overview tab that needs to be manually populated too.
 This page will be populated with stand-alone widgets or card widgets.
 
-Often, one will want to have one single stand-alone widget to represent a single Equipment, for example a thermostat or a Chomecast.
+Often, one will want to have one single stand-alone widget to represent a single Equipment, for example a thermostat or a Chromecast.
 These will be a single card that provides the display and interaction with many Items.
 If one has more than one Equipment that will use the same widget, or the widget is complex, create a custom widget for these.
 Once created, apply the custom widget to the Equipment Group Item in the model.
@@ -413,7 +413,7 @@ For this tutorial we will have two rows and three columns.
 
 ![Overview row and columns](images/overview_row_and_columns.png)
 
-Now we will add a custom widget to that first columnn.
+Now we will add a custom widget to that first column.
 In this case we will add a garage door widget that includes a camera feed, shows the door status, and allows triggering two garage doors.
 Click on the + in that first cell and select the desired widget from the list.
 This is a simple widget that doesn't use any properties, so we are done.