Update backlog_count_hint docstring (#413)

Author: Sushisource

openapi/openapiv2.json

@@ -6569,7 +6569,7 @@
         "backlogCountHint": {
           "type": "string",
           "format": "int64",
-          "description": "A hint that there are more tasks already present in this task queue. Can be used to\nprioritize draining a sticky queue before polling from a normal queue."
+          "description": "A hint that there are more tasks already present in this task queue \npartition. Can be used to prioritize draining a sticky queue.\n\nSpecifically, the returned number is the number of tasks remaining in\nthe in-memory buffer for this partition, which is currently capped at\n1000. Because sticky queues only have one partition, this number is \nmore useful when draining them. Normal queues, typically having more than one \npartition, will return a number representing only some portion of the \noverall backlog. Subsequent RPCs may not hit the same partition as \nthis call."
         },
         "history": {
           "$ref": "#/definitions/v1History",

openapi/openapiv3.yaml

@@ -4474,9 +4474,7 @@ components:
           format: int32
         backlogCountHint:
           type: string
-          description: |-
-            A hint that there are more tasks already present in this task queue. Can be used to
-             prioritize draining a sticky queue before polling from a normal queue.
+          description: "A hint that there are more tasks already present in this task queue \n partition. Can be used to prioritize draining a sticky queue.\n\n Specifically, the returned number is the number of tasks remaining in\n the in-memory buffer for this partition, which is currently capped at\n 1000. Because sticky queues only have one partition, this number is \n more useful when draining them. Normal queues, typically having more than one \n partition, will return a number representing only some portion of the \n overall backlog. Subsequent RPCs may not hit the same partition as \n this call."
         history:
           allOf:
             - $ref: '#/components/schemas/History'

temporal/api/workflowservice/v1/request_response.proto

@@ -278,8 +278,16 @@ message PollWorkflowTaskQueueResponse {
     int64 started_event_id = 5;
     // Starting at 1, the number of attempts to complete this task by any worker.
     int32 attempt = 6;
-    // A hint that there are more tasks already present in this task queue. Can be used to
-    // prioritize draining a sticky queue before polling from a normal queue.
+    // A hint that there are more tasks already present in this task queue 
+    // partition. Can be used to prioritize draining a sticky queue.
+    //
+    // Specifically, the returned number is the number of tasks remaining in
+    // the in-memory buffer for this partition, which is currently capped at
+    // 1000. Because sticky queues only have one partition, this number is 
+    // more useful when draining them. Normal queues, typically having more than one 
+    // partition, will return a number representing only some portion of the 
+    // overall backlog. Subsequent RPCs may not hit the same partition as 
+    // this call.
     int64 backlog_count_hint = 7;
     // The history for this workflow, which will either be complete or partial. Partial histories
     // are sent to workers who have signaled that they are using a sticky queue when completing