doc: remove references to WpImplEndpoint that is now private

lib/wp/endpoint.c

@@ -15,10 +15,6 @@
  *
  * A #WpEndpoint is constructed internally when a new endpoint appears on the
  * PipeWire registry and it is made available through the #WpObjectManager API.
- *
- * A #WpImplEndpoint allows implementing an endpoint and exporting it to
- * PipeWire, which is done by augmenting the #WpImplEndpoint with
- * %WP_PROXY_FEATURE_BOUND.
  */
 
 #include "endpoint.h"

lib/wp/object-manager.c

@@ -22,9 +22,9 @@
  *     that created them appears in the #WpObjectManager (as soon as its
  *     %WP_PROXY_FEATURE_BOUND is enabled)
  *   * local PipeWire objects that are being exported to PipeWire
- *     (#WpImplNode, #WpImplEndpoint, etc); these appear in the #WpObjectManager
- *     as soon as they are exported (so, when their %WP_PROXY_FEATURE_BOUND
- *     is enabled)
+ *     (#WpImplNode, WpImplEndpoint [private], etc); these appear in the
+ *     #WpObjectManager as soon as they are exported (so, when their
+ *     %WP_PROXY_FEATURE_BOUND is enabled)
  *   * WirePlumber-specific objects, such as WirePlumber factories
  *
  * To start an object manager, you first need to declare interest in a certain