Merge branch 'main' into metofficedatahubV4

concepts/profiles.md

@@ -5,7 +5,7 @@ title: Profiles
 
 # Profiles
 
-The communication between the framework and the Thing handlers is managed by the "Communication Manager", which in turn uses "Profiles"  to determined what exactly needs to be done.
+The communication between the framework and the Thing handlers is managed by the "Communication Manager", which in turn uses "Profiles" to determine what exactly needs to be done.
 This provides some flexibility to influence these communication paths.
 
 By their nature, profiles are correlated to links between Items and Channels (i.e. `ItemChannelLinks`). So if one Channel is linked to several Items it also will have several profile instances, each handling the communication to exactly one of these Items.

developers/bindings/index.md

@@ -572,6 +572,7 @@ If you implement the `ThingActions` interface, you can tell the framework about
 Please note that for actions not related to Things you will instead implement an `ActionHandler` as described in the developing [Module Types](../module-types/) chapter.
 
 You start things off by implementing `ThingActions` and annotate your class with `@ThingActionsScope`.
+The scope name should be the binding name, but it can also be bindingname-xxx when you need several scopes (for different thing types).
 Since a new service is required for each thing, the component needs to be a `PROTOTYPE`:
 
 ```java