Update typing event and timeout parameter names, updating default for heartbeatThrottleMs

Author: splindsay-92

content/chat/rooms/typing.textile

@@ -73,7 +73,7 @@ The following is the structure of a typing event:
     "zoranges",
   },
   "change": {
-    "event": "typing.started",
+    "type": "typing.started",
     "clientId": "clemons"
   }
 }
@@ -84,6 +84,8 @@ The following are the properties of a typing event:
 |_. Property |_. Description |_. Type |
 | currentlyTyping | A set of all users currently typing. | Set |
 | change | The single change that resulted in the event. | Object |
+| | type: The type of change that occurred. | String |
+| | clientId: The @clientId@ of the user that triggered the change. | String |
 
 You can use the size of the @currentlyTyping@ set to decide whether to display individual user names, or that multiple people are typing in your user interface.
 
@@ -135,11 +137,11 @@ blang[javascript,swift,kotlin].
 blang[react].
   Use the "@start()@":https://sdk.ably.com/builds/ably/ably-chat-js/main/typedoc/interfaces/chat-react.UseTypingResponse.html#start method available from the response of the @useTyping@ hook to emit an event when a user has started typing.
 
-There is a timeout associated with start events. On first calling `start()`, this timer is set, subsequent calls to `start()` before the timer expires will result in a no-op. The length of this timeout is customizable using the @heartbeatIntervalMs@ parameter that can be configured in the @RoomOptions@ that you set when you "create a room":/docs/chat/rooms#create. The default is 15000ms.
+There is a timeout associated with start events. On first calling `start()`, this timer is set, subsequent calls to `start()` before the timer expires will result in a no-op. The length of this timeout is customizable using the @heartbeatThrottleMs@ parameter that can be configured in the @RoomOptions@ that you set when you "create a room":/docs/chat/rooms#create. The default is 10000ms.
 
 Consequently, if you want to keep the typing indicator active, you should call `start()` with each key press to ensure a new typing event is emitted after the timeout has expired.
 
-For a client receiving typing events, the typing indicator they have received will remain active for the duration of the timeout, plus a predefined grace period of 2000ms. If a new typing event is received for the same user before the grace period has expired, the typing indicator will be reset to the full duration of the timeout. For example, if the timeout is 15000ms, the typing indicator will remain active for 17000ms.
+For a client receiving typing events, the typing indicator they have received will remain active for the duration of the timeout, plus a predefined grace period of 2000ms. If a new typing event is received for the same user before the grace period has expired, the typing indicator will be reset to the full duration of the timeout. For example, if the timeout is 15000ms, the typing indicator will remain active for 12000ms.
 
 <aside data-type='note'>
 <p>It is important for all clients in a room to have the same timeout value set, otherwise the typing indicators may not be displayed correctly.</p>