From 1848f726728f4d2ff6f40d45935c9e7e55d03c34 Mon Sep 17 00:00:00 2001 From: Clemens Linnhoff Date: Mon, 28 Aug 2023 14:29:24 +0200 Subject: [PATCH] Update model_types.adoc Exchange 'also' for 'additionally' the clarify, that the mentioned OSI messages can be defined in addition to SensorView and TrafficUpdate. --- doc/spec/model_types.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/spec/model_types.adoc b/doc/spec/model_types.adoc index 3882bb7..778d0c4 100644 --- a/doc/spec/model_types.adoc +++ b/doc/spec/model_types.adoc @@ -23,8 +23,8 @@ This model type is used to model whole traffic participants, such as vehicles or Traffic participant models may internally use environmental effect models, sensor models, or logical models as part of a modeled autonomous vehicle. They may also be used to implement surrounding traffic in simplified ways. Traffic participant models consume `osi3::SensorView` as input and produce `osi3::TrafficUpdate` as output. -They may also consume `osi3::TrafficCommand` as input to allow control by a scenario engine or other coordinating function. -They may also produce `osi3::TrafficCommandUpdate` as output to allow status responses to such control messages. +They may additionally consume `osi3::TrafficCommand` as input to allow control by a scenario engine or other coordinating function. +They may additionally produce `osi3::TrafficCommandUpdate` as output to allow status responses to such control messages. Streaming update consumer models:: This model type receives a streaming update input for further processing.