docs: minor fixes as requested from code review

Co-authored-by: danielpeintner <daniel.peintner@gmail.com>

Author: relu91

README.md

@@ -325,7 +325,7 @@ Below are small explanations of what they can be used for:
 
 node-wot allows configuration of "Data Mapping" which extracts specific values from a Thing's response object (e.g., getting `123` from a wrapper `{ value: 123, timestamp: ... }`). This is useful when the Interaction only cares about an inner value but the Thing returns a wrapper object.
 
-This is configured using the experimental `nw:dataSchemaMapping` vocabulary in the Thing Description. It can be defined at the Thing level or globally injected via the `Servient` configuration:
+This is configured using the experimental node-wot `nw:dataSchemaMapping` vocabulary in the Thing Description. It can be defined at the Thing level or globally injected via the `Servient` configuration:
 
 ```json
 {

packages/core/src/wot-impl.ts

@@ -109,7 +109,7 @@ export default class WoTImpl {
             const thing = parseTD(JSON.stringify(td), true);
             const mapping = { ...(this.srv.dataSchemaMapping ?? {}), ...(thing["nw:dataSchemaMapping"] ?? {}) };
 
-            // If none mapping is configured, the property will be left undefined
+            // If no mapping is configured, the property will be left undefined
             if (Object.keys(mapping).length > 0) {
                 thing["nw:dataSchemaMapping"] = mapping;
             }