Typos (#2078)

Add an example to Group item, that it can reference sub-types of
Number (dimensions).

configuration/items.md

@@ -523,13 +523,13 @@ Incompatible Item types within a Group may result in the invalid aggregation res
 Examples for derived states on Group Items when declared in the Item DSL:
 
 ```java
-Group:Number                Lights        "Active Lights [%d]"              // e.g. "2"
-Group:Switch:OR(ON,OFF)     Lights        "Active Lights [%d]"              // e.g. ON and "2"
-Group:Switch:AND(ON,OFF)    Lights        "Active Lights [%d]"              // e.g. ON and "2"
-Group:Number:AVG            Temperatures  "All Room Temperatures [%.1f °C]" // e.g. "21.3 °C"
-Group:DateTime:EARLIEST     LatestUpdate "Latest Update [%1$tY.%1$tm.%1$tY %1$tH:%1$tM:%1$tS]"
-Group:DateTime:LATEST       LastSeen  "Last Seen [%1$tY.%1$tm.%1$tY %1$tH:%1$tM:%1$tS]"
-Group:Number:COUNT("OFFLINE")     OfflineDevices "Offline Devices [%d]"     // e.g. "2"
+Group:Number                  Lights       "Active Lights [%d]"              // e.g. "2"
+Group:Switch:OR(ON,OFF)       Lights       "Active Lights [%d]"              // e.g. ON and "2"
+Group:Switch:AND(ON,OFF)      Lights       "Active Lights [%d]"              // e.g. ON and "2"
+Group:Number:Temperature:AVG  Temperatures "All Room Temperatures [%.1f °C]" // e.g. "21.3 °C"
+Group:DateTime:EARLIEST       LatestUpdate "Latest Update [%1$tY.%1$tm.%1$tY %1$tH:%1$tM:%1$tS]"
+Group:DateTime:LATEST         LastSeen     "Last Seen [%1$tY.%1$tm.%1$tY %1$tH:%1$tM:%1$tS]"
+Group:Number:COUNT("OFFLINE") OfflineDevices "Offline Devices [%d]"     // e.g. "2"
 ```
 
 The first three examples above compute the number of active lights and store them as group state.

tutorials/getting_started/item_widgets.md

@@ -35,7 +35,7 @@ For complicated expressions, gradually build up the expression in this tool unti
 
 ## Visibility
 
-Each custom defined widget has a "Visibility" and "Visible to" property.
+Each custom defined widget has a "Visibility" and a "Visible to" property.
 The "Visibility" option takes a boolean `true` or `false` or the result of a boolean expression to determine whether or not to render the widget.
 The "Visibile to" property controls which type of user can see the widget.
 Take heed of the warning, this is not a security feature, but it can be used to limit what a regular user can see in the automatically generated parts of the Overview Page.

ui/layout-pages.md

@@ -202,7 +202,7 @@ _Screen Width:_
 Screen width in CSS pixels. Defaults to 1280.
 
 _Screen Height:_
-Screen width in CSS pixels. Defaults to 720.
+Screen height in CSS pixels. Defaults to 720.
 
 _Scaling:_
 Enabling this scales the defined screen to the width available in the browser window.
@@ -257,7 +257,7 @@ _Screen Width:_
 Screen width in CSS pixels. Defaults to 1280.
 
 _Screen Height:_
-Screen width in CSS pixels. Defaults to 720.
+Screen height in CSS pixels. Defaults to 720.
 
 _Scaling:_
 Enabling this scales the defined screen to the width available in the browser window. All widgets are resized accordingly.