From 10faa44da9134c053c28a55857068909ca29a452 Mon Sep 17 00:00:00 2001 From: Gold Edem Hogan Date: Wed, 23 Aug 2023 11:29:59 +0000 Subject: [PATCH] doc: fix a couple typos PR #1068 --- src/regex/bytes.rs | 2 +- src/regex/string.rs | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/regex/bytes.rs b/src/regex/bytes.rs index 03982544b..cc53482cb 100644 --- a/src/regex/bytes.rs +++ b/src/regex/bytes.rs @@ -1154,7 +1154,7 @@ impl Regex { /// /// A [`CaptureLocations`] stores the same byte offsets as a [`Captures`], /// but does *not* store a reference to the haystack. This makes its API - /// a bit lower level and less convenience. But in exchange, callers + /// a bit lower level and less convenient. But in exchange, callers /// may allocate their own `CaptureLocations` and reuse it for multiple /// searches. This may be helpful if allocating a `Captures` shows up in a /// profile as too costly. diff --git a/src/regex/string.rs b/src/regex/string.rs index b9a3c3390..d5908ae0d 100644 --- a/src/regex/string.rs +++ b/src/regex/string.rs @@ -1145,7 +1145,7 @@ impl Regex { /// /// A [`CaptureLocations`] stores the same byte offsets as a [`Captures`], /// but does *not* store a reference to the haystack. This makes its API - /// a bit lower level and less convenience. But in exchange, callers + /// a bit lower level and less convenient. But in exchange, callers /// may allocate their own `CaptureLocations` and reuse it for multiple /// searches. This may be helpful if allocating a `Captures` shows up in a /// profile as too costly.