From 8bd3b8ff291d4f59d7aa8a3a4dd674437e77e8b5 Mon Sep 17 00:00:00 2001
From: Mikko Lehto <mslehto@iki.fi>
Date: Fri, 2 Dec 2016 11:01:08 +0200
Subject: [PATCH] modules/rtpproxy: documentation typo fix and rephrase

---
 modules/rtpproxy/doc/rtpproxy_admin.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/modules/rtpproxy/doc/rtpproxy_admin.xml b/modules/rtpproxy/doc/rtpproxy_admin.xml
index 49edff78625..d0db7d8a70c 100644
--- a/modules/rtpproxy/doc/rtpproxy_admin.xml
+++ b/modules/rtpproxy/doc/rtpproxy_admin.xml
@@ -456,7 +456,7 @@ rtpproxy_offer();
 				So, for example if a SIP requests is processed with 'ie' flags, the corresponding
 				response must be processed with 'ie' flags.
 				</para><para>
-				Note: As rtpproxy in bridge mode s per default asymmetric, you have to specify
+				Note: As rtpproxy in bridge mode is asymmetric per default, you have to specify
 				the 'w' flag for clients behind NAT! See also above notes!
 				</para></listitem>
 				<listitem><para>
@@ -764,7 +764,7 @@ rtpproxy_manage();
 ...
     if (is_method("INVITE")) {
         rtpproxy_offer();
-        if (detect_hold()) {
+        if (is_audio_on_hold()) {
             rtpproxy_stream2uas("/var/rtpproxy/prompts/music_on_hold", "-1");
         } else {
             rtpproxy_stop_stream2uas();