From ba409a420bbf836de9556f89fd5f1a9622b8e834 Mon Sep 17 00:00:00 2001
From: Ralph Giles <giles@mozilla.com>
Date: Fri, 17 Oct 2014 16:35:50 -0700
Subject: [PATCH] oggopus: use 'invalid' to match other occurances and RFC
 6716.

Suggestion from mark4o.
---
 doc/draft-ietf-codec-oggopus.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/draft-ietf-codec-oggopus.xml b/doc/draft-ietf-codec-oggopus.xml
index 5c755c9d6..25af44869 100644
--- a/doc/draft-ietf-codec-oggopus.xml
+++ b/doc/draft-ietf-codec-oggopus.xml
@@ -182,7 +182,7 @@ All of the Opus packets in a single Ogg packet MUST be constrained to have the
  same duration.
 A decoder SHOULD treat any Opus packet whose duration is different from that of
  the first Opus packet in an Ogg packet as if it were an Opus packet with an
- illegal TOC sequence.
+ invalid TOC sequence.
 </t>
 <t>
 The coding mode (SILK, Hybrid, or CELT), audio bandwidth, channel count,
@@ -199,7 +199,7 @@ The first audio data page SHOULD NOT have the 'continued packet' flag set
 Packets MUST be placed into Ogg pages in order until the end of stream.
 Audio packets MAY span page boundaries.
 A decoder MUST treat a zero-octet audio data packet as if it were an Opus
- packet with an illegal TOC sequence.
+ packet with an invalid TOC sequence.
 The last page SHOULD have the 'end of stream' flag set, but implementations
  need to be prepared to deal with truncated streams that do not have a page
  marked 'end of stream'.
-- 
GitLab