fixed disposed and ringing events docs

Author: byrnereese

docs/events/disposed.md

@@ -1,11 +1,11 @@
-# webPhone.on('disposed', callback)
+# callSession.on('disposed', callback)
 
 This event is triggered when the web phone instance is properly disposed of. This event does not fire when an instance [expires](../get-started/instances.md#instance-expiry). This event is useful if garbage collection is required when web phone are disposed of. 
 
 ## Sample
 
 ```ts
-webPhone.on("disposed", () => {
+callSession.on("disposed", () => {
   // do something with the inbound call
 });
 ```

docs/events/ringing.md

@@ -1,4 +1,4 @@
-# webPhone.on('ringing', callback)
+# callSession.on('ringing', callback)
 
 This event is triggered when a call is connected and it is ringing. It is an event that has very little utility, because when you make an outbound call, or by the time you receive an inbound call event, by the time the `callSession` object is returned, the phone is already ringing. 
 
@@ -19,5 +19,5 @@ Therefore, these two code samples are functionally equivalent to the `ringing` e
 ## Sample
 
 ```js
-webPhone.on('ringing', callSession => {...})
+callSession.on('ringing', callSession => {...})
 ```

mkdocs.yml

@@ -85,13 +85,13 @@ nav:
 - 'Events':
   - 'Subscribing to events': events/index.md
   - 'WebPhone events':
-    - 'disposed': events/disposed.md
     - 'inboundCall': events/inboundCall.md
     - 'outboundCall': events/outboundCall.md
-    - 'ringing': events/ringing.md
   - 'Call Session events':
     - 'answered': events/answered.md
+    - 'disposed': events/disposed.md
     - 'inboundMessage': events/inboundMessage.md
+    - 'ringing': events/ringing.md
     - 'outboundMessage': events/outboundMessage.md
 - 'Reference':
   - 'Overview': reference/index.md