improved single room vs multi room explanation

proto/cmp/services/accommodation/v1alpha1/search.proto

@@ -24,14 +24,22 @@ import "cmp/types/v1alpha1/traveller.proto";
 //
 // The `Accommodation Search Request` message type facilitates the request for
 // accommodations like hotel and holiday home searches within the platform. In the
-// request the market, language and currency are specified at the top-level. In the
-// Unit we specify the details of the trip like dates, properties or locations or
+// request the market, language and currency are specified at the top-level. 
+// 
+// In the Unit we specify the details of the trip like dates, properties or locations or
 // filters. The purpose of such a structure is to allow for multi-room and
-// multi-property searches, so that several rooms or houses can be requested for the
-// same dates and location or for the purpose of a tour or roadtrip, several
-// accommodations for sequential dates and different locations.
+// multi-property searches.
+// This means that there is no grouping of different room, mealplan or rateplan options
+// in single room or single property searches. Each AccommodationSearchResult is one 
+// bookable option.
 //
-// Developers leveraging this message type should ensure proper validation and
+// Several rooms or houses can be requested for the same dates and location or 
+// for the purpose of a tour or roadtrip, several accommodations or properties for 
+// sequential dates and different locations. This is done by specifying multiple Units
+// for the same or different periods, the same or different accommodations or properties,
+// specifying which travellers sleep in which unit.
+// 
+//// Developers leveraging this message type should ensure proper validation and
 // handling, especially considering fields that are still under review, like
 // `speech_request`.
 message AccommodationSearchRequest {