From 08fa8a6e5ff18c6013a99ee4ea0906649cc6e96e Mon Sep 17 00:00:00 2001
From: Leif Madsen <leif@leifmadsen.com>
Date: Wed, 10 Mar 2010 20:53:43 +0000
Subject: [PATCH] Be less ambiguous in Record() app docs. For some reason the
 documentation for the 'k' application in trunk and 1.6.2 is different than
 1.6.0 and 1.6.1, so I'm setting them all to match. The wording in 1.6.2 and
 trunk was ambiguous, so you could interpret the wording the mean that
 recording would continue upon hangup indefinitely, or you could interpret it
 to mean that the recorded data would not be discarded upon hangup. This
 change makes it clear we mean the latter, and not the former.

Came from a discussion in #asterisk on IRC.

git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@251680 65c4cc65-6c06-0410-ace0-fbb531ad65f3
---
 apps/app_record.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/apps/app_record.c b/apps/app_record.c
index 14b665d307..64e635018b 100644
--- a/apps/app_record.c
+++ b/apps/app_record.c
@@ -76,7 +76,7 @@ ASTERISK_FILE_VERSION(__FILE__, "$Revision$")
 						<para>Ignore all terminator keys (DTMF) and keep recording until hangup.</para>
 					</option>
 					<option name="k">
-					        <para>Keep recording if channel hangs up.</para>
+					        <para>Keep recorded file upon hangup.</para>
 					</option>
 					<option name="y">
 					        <para>Terminate recording if *any* DTMF digit is received.</para>
-- 
GitLab