Update Copyrights

Author: jason-fox

README.ja.md

@@ -1543,4 +1543,4 @@ curl -iX DELETE \
 
 ## ライセンス
 
-[MIT](LICENSE) © 2021-2025 FIWARE Foundation e.V.
+[MIT](LICENSE) © 2021-2026 FIWARE Foundation e.V.

README.md

@@ -17,8 +17,8 @@
 This tutorial a wires up the dummy [JSON](https://json.org/)-based IoT devices using the
 [IoT Agent for JSON](https://fiware-iotagent-json.readthedocs.io/en/latest/usermanual/index.html#user-programmers-manual)
 devices so that measurements can be read and commands can be sent using
-[NGSI LD](https://cim.etsi.org/NGSI-LD/official/front-page.html) requests sent to an
-NGSI-LD compliant context broker such as the [Orion Context Broker](https://fiware-orion.readthedocs.io/en/latest/).
+[NGSI LD](https://cim.etsi.org/NGSI-LD/official/front-page.html) requests sent to an NGSI-LD compliant context broker
+such as the [Orion Context Broker](https://fiware-orion.readthedocs.io/en/latest/).
 
 The tutorial uses [cUrl](https://ec.haxx.se/) commands throughout, but is also available as
 [Postman documentation](https://fiware.github.io/tutorials.IoT-Agent-JSON/ngsi-ld.html)
@@ -110,7 +110,7 @@ A direct comparison of the two IoT Agents can be seen below:
 | HTTP commands posted to a well-known URL - response is in the reply | HTTP commands posted to a well-known URL - response is in the reply | Communications Handshake   |
 | MQTT devices are identified by the path of the topic `/XXX/YYY`     | MQTT devices are identified by the path of the topic `/XXX/YYY`     | Device Identification      |
 | MQTT commands posted to the `cmd` topic                             | MQTT commands posted to the `cmd` topic                             | Communications Handshake   |
-| MQTT command responses posted to the `cmdexe` topic                 | MQTT command responses posted responses to the `cmdexe` topic                          | Communications Handshake   |
+| MQTT command responses posted to the `cmdexe` topic                 | MQTT command responses posted responses to the `cmdexe` topic       | Communications Handshake   |
 
 As can be seen, the message payload differs entirely between the two IoT Agents, but much of the rest of the protocol
 remains the same.
@@ -588,11 +588,11 @@ however it has been included here for completeness.
 
 ### Provisioning a Sensor
 
-The NGSI-LD [specification](https://cim.etsi.org/NGSI-LD/official/front-page.html)
-mandates full URNs when creating context data entities, however the incoming messages from the devices will not be aware
-of this convention. Furthermore the attribute name on the context data entity should match the short names found within
-the associated `@context` file. These mappings can be defined at the service group level as seen in the previous
-request, or they can be defined by provisioning each device individually.
+The NGSI-LD [specification](https://cim.etsi.org/NGSI-LD/official/front-page.html) mandates full URNs when creating
+context data entities, however the incoming messages from the devices will not be aware of this convention. Furthermore
+the attribute name on the context data entity should match the short names found within the associated `@context` file.
+These mappings can be defined at the service group level as seen in the previous request, or they can be defined by
+provisioning each device individually.
 
 Three types of measurement attributes can be provisioned:
 
@@ -1500,4 +1500,4 @@ the other [tutorials in this series](https://ngsi-ld-tutorials.rtfd.io)
 
 ## License
 
-[MIT](LICENSE) © 2021-2025 FIWARE Foundation e.V.
+[MIT](LICENSE) © 2021-2026 FIWARE Foundation e.V.