# An error in documentation?

**URL:** <https://mediasoup.discourse.group/t/an-error-in-documentation/5341>\
**Category:** mediasoup libraries\
**Created:** [July 7, 2023, 12:50pm UTC](https://mediasoup.discourse.group/t/an-error-in-documentation/5341 "2023-07-07T12:50:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ashmig](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ashmig/32/2255_2.png) [@ashmig](https://mediasoup.discourse.group/u/ashmig)\
**Post date:** [July 7, 2023, 12:50pm UTC](https://mediasoup.discourse.group/t/an-error-in-documentation/5341/1 "2023-07-07T12:50:51Z")

</div>

Link: [mediasoup :: Communication Between Client and Server](https://mediasoup.org/documentation/v3/communication-between-client-and-server/)

Quote:

> The same happens when pausing a RTP producer or consumer in client or server side. The action must be signaled to the other side. In addition, the server side application should listen for the following events and notify the client about them:
> 
> - Consumer [“producerpause”](https://mediasoup.org/documentation/v3/mediasoup/api/#consumer-on-producerpause). The client should call `pause()` on the corresponding local transport.
> - Consumer [“producerresume”](https://mediasoup.org/documentation/v3/mediasoup/api/#consumer-on-producerresume). The client should call `resume()` on the corresponding local transport (unless the consumer itself was also paused on purpose).

Do we really need to pause / resume `local transport`, but not `local consumer` on a client side?

---

<div class="post-metadata">

**Author:** ![ibc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ibc/32/1540_2.png) [@ibc](https://mediasoup.discourse.group/u/ibc)\
**Post date:** [July 10, 2023, 10:31am UTC](https://mediasoup.discourse.group/t/an-error-in-documentation/5341/2 "2023-07-10T10:31:22Z")

</div>

> [@ashmig](#):
>
> on the corresponding local transport

It should be “local consumer”. Fixed and pushed. Thanks.