Fixing build errors

content/en/docs/concepts/development_model/vehicle_app_manifest/interfaces/grpc_interface.md

@@ -62,7 +62,7 @@ You need to specify `devenv-devcontainer-setup` >= `v2.4.2` in your project conf
   },
   "components": [
     {
-      "id": "grpc-interface-support", 
+      "id": "grpc-interface-support",
     }
   ],
 }

content/en/docs/tutorials/vehicle_app_development/cpp_development.md

@@ -157,7 +157,7 @@ try {
     // thrown by .value(): The vehicle speed signal does not contain a valid value, currently
 }
 ```
-* Throwing the `InvalidValueException` can be avoided if you first check that `.isValid()` returns true before calling `.value()`: 
+* Throwing the `InvalidValueException` can be avoided if you first check that `.isValid()` returns true before calling `.value()`:
 ```Cpp
 auto vehicleSpeed = Vehicle.Speed.get()->await();
 if (vehicleSpeed.isValid())

content/en/docs/tutorials/vehicle_model_creation/manual_model_creation/_index.md

@@ -20,7 +20,7 @@ This tutorial will show you how to:
 {{% alert title="Note" %}}
 A _Vehicle Model_ should be defined in its own package. This makes it possible to distribute the _Vehicle Model_ later as a standalone package and to use it in different _Vehicle App_ projects.
 
-The creation of a new vehicle model is only required if the vehicle signals (like sensors and actuators) defined in the current version of the [COVESA Vehicle Signal Specification](https://covesa.github.io/vehicle_signal_specification/) (VSS) is not sufficient for the definition of your vehicle API. Otherwise you could use the default vehicle model we already generated for you, see [Python Vehicle Model](https://github.com/eclipse-velocitas/vehicle-model-python) and [C++ Vehicle Model](https://github.com/eclipse-velocitas/vehicle-model-cpp).  
+The creation of a new vehicle model is only required if the vehicle signals (like sensors and actuators) defined in the current version of the [COVESA Vehicle Signal Specification](https://covesa.github.io/vehicle_signal_specification/) (VSS) is not sufficient for the definition of your vehicle API. Otherwise you could use the default vehicle model we already generated for you, see [Python Vehicle Model](https://github.com/eclipse-velocitas/vehicle-model-python) and [C++ Vehicle Model](https://github.com/eclipse-velocitas/vehicle-model-cpp).
 {{% /alert %}}
 
 ## Create a Vehicle Model from VSS specification