update descriptions to specify order

Co-authored-by: John Jannotti <john.jannotti@algorand.com>

daemon/algod/api/algod.oas2.json

@@ -4519,7 +4519,7 @@
       }
     },
     "AppCallLogs": {
-      "description": "The logged messages from an app call along with the app ID and outer transaction ID.",
+      "description": "The logged messages from an app call along with the app ID and outer transaction ID. Logs appear in the same order that they were emitted.",
       "type": "object",
       "required": [
         "logs",
@@ -5202,7 +5202,7 @@
       }
     },
     "BlockLogsResponse": {
-      "description": "All of the logs from outer and inner app calls in the given round. Each app call results in a new AppCallLogs object, thus there might be multiple objects with the same application ID and outer transaction ID in the event of multiple inner app calls to the same app. App calls with no logs are not included in the response.",
+      "description": "All logs emitted in the given round. Each app call, whether top-level or inner, that contains logs results in a separate AppCallLogs object. Therefore there may be multiple AppCallLogs with the same application ID and outer transaction ID in the event of multiple inner app calls to the same app. App calls with no logs are not included in the response. AppCallLogs are returned in the same order that their corresponding app call appeared in the block (pre-order traversal of inner app calls)",
       "schema": {
         "type": "object",
         "required": [

daemon/algod/api/algod.oas3.yml

@@ -342,7 +342,7 @@
             }
           }
         },
-        "description": "All of the logs from outer and inner app calls in the given round. Each app call results in a new AppCallLogs object, thus there might be multiple objects with the same application ID and outer transaction ID in the event of multiple inner app calls to the same app. App calls with no logs are not included in the response."
+        "description": "All logs emitted in the given round. Each app call, whether top-level or inner, that contains logs results in a separate AppCallLogs object. Therefore there may be multiple AppCallLogs with the same application ID and outer transaction ID in the event of multiple inner app calls to the same app. App calls with no logs are not included in the response. AppCallLogs are returned in the same order that their corresponding app call appeared in the block (pre-order traversal of inner app calls)"
       },
       "BlockResponse": {
         "content": {
@@ -1237,7 +1237,7 @@
         "type": "object"
       },
       "AppCallLogs": {
-        "description": "The logged messages from an app call along with the app ID and outer transaction ID.",
+        "description": "The logged messages from an app call along with the app ID and outer transaction ID. Logs appear in the same order that they were emitted.",
         "properties": {
           "application-index": {
             "description": "The application from which the logs were generated",
@@ -4073,7 +4073,7 @@
                 }
               }
             },
-            "description": "All of the logs from outer and inner app calls in the given round. Each app call results in a new AppCallLogs object, thus there might be multiple objects with the same application ID and outer transaction ID in the event of multiple inner app calls to the same app. App calls with no logs are not included in the response."
+            "description": "All logs emitted in the given round. Each app call, whether top-level or inner, that contains logs results in a separate AppCallLogs object. Therefore there may be multiple AppCallLogs with the same application ID and outer transaction ID in the event of multiple inner app calls to the same app. App calls with no logs are not included in the response. AppCallLogs are returned in the same order that their corresponding app call appeared in the block (pre-order traversal of inner app calls)"
           },
           "400": {
             "content": {