media_exchange: document RTP Relay migration

modules/media_exchange/doc/media_exchange_admin.xml

@@ -37,9 +37,9 @@
 		<listitem>
 		<para>
 			<emphasis>Fork Media</emphasis> - the new B2B call, either originated
-			or terminated, will just have a copy of the RTP forked by RTPProxy. In
-			this mode, the proxied call should have had RTPProxy already engaged in
-			the media path before the forked call starts. One can fork only one
+			or terminated, will just have a copy of the RTP forked by the media
+			proxy engine. In this mode, the proxied call should have had the RTP
+			relay engaged path before the forked call starts. One can fork only one
 			media leg, or both legs. <emphasis>NOTE:</emphasis> RTPProxy currently
 			does not support stopping media streaming, therefore if the streaming
 			call terminates, RTPProxy will continue streaming, even if there is no
@@ -94,8 +94,8 @@
 			</listitem>
 			<listitem>
 			<para>
-				<emphasis>RTPProxy</emphasis> - optional, the RTPProxy module is
-					only used when running in media forking mode.
+				<emphasis>RTP Relay</emphasis> - optional, when the initial
+				call either uses RTP Relay, or when using the media forking mode.
 			</para>
 			</listitem>
 			<listitem>