From 20f834b9abe9f8a19562dc787d5085e59e57e695 Mon Sep 17 00:00:00 2001
From: Todd Fiala <todd.fiala@gmail.com>
Date: Wed, 4 Jun 2014 05:07:40 +0000
Subject: [PATCH] Fix a couple minor typos in $qMemoryRegionInfo packet docs.

llvm-svn: 210163
---
 lldb/docs/lldb-gdb-remote.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/lldb/docs/lldb-gdb-remote.txt b/lldb/docs/lldb-gdb-remote.txt
index cc4fb5d..d15cc72 100644
--- a/lldb/docs/lldb-gdb-remote.txt
+++ b/lldb/docs/lldb-gdb-remote.txt
@@ -791,7 +791,7 @@ not supported.
 // "qMemoryRegionInfo:<addr>"
 //
 // BRIEF
-//  Get information about the address the range that contains "<addr>"
+//  Get information about the address range that contains "<addr>"
 //
 // PRIORITY TO IMPLEMENT
 //  Medium. This is nice to have, but it isn't necessary. It helps LLDB
@@ -809,7 +809,7 @@ We added a way to get information for a memory region. The packet is:
     
 Where <addr> is a big endian hex address. The response is returned in a series
 of tuples like the data returned in a stop reply packet. The currently valid
-tuples tp return are:
+tuples to return are:
 
     start:<start-addr>; // <start-addr> is a big endian hex address that is 
                         // the start address of the range that contains <addr>
-- 
2.7.4