From dfbcf357b87072370b86d97e122ff3efc615ae15 Mon Sep 17 00:00:00 2001
From: 8573 <8573@users.noreply.github.com>
Date: Sat, 25 Jun 2022 03:46:37 -0700
Subject: [PATCH] Copyedit RUSTSEC-2021-0122

Apply some copyedits to the text introduced by #1268.  Add a missing
comma; inflect "be" better; and use normal quotation marks rather than
backticks around the word "safe", referring to Safe Rust, as, unlike
`unsafe`, "safe" is not Rust syntax.
---
 crates/flatbuffers/RUSTSEC-2021-0122.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/crates/flatbuffers/RUSTSEC-2021-0122.md b/crates/flatbuffers/RUSTSEC-2021-0122.md
index ecce19071..cb04b183e 100644
--- a/crates/flatbuffers/RUSTSEC-2021-0122.md
+++ b/crates/flatbuffers/RUSTSEC-2021-0122.md
@@ -15,9 +15,9 @@ patched = []
 Code generated by flatbuffers' compiler is `unsafe` but not marked as such.
 See https://github.com/google/flatbuffers/issues/6627 for details.
 
-For example, if generated code is used to decode malformed or untrusted input
-undefined behavior (and thus security vulnerabilities) are possible even without
-the use of the `unsafe` keyword, [violating the the meaning of `safe`](https://doc.rust-lang.org/std/keyword.unsafe.html#the-different-meanings-of-unsafe) code;
+For example, if generated code is used to decode malformed or untrusted input,
+undefined behavior (and thus security vulnerabilities) is possible even without
+the use of the `unsafe` keyword, [violating the the meaning of "safe"](https://doc.rust-lang.org/std/keyword.unsafe.html#the-different-meanings-of-unsafe) code;
 
 All users that use generated code by `flatbuffers` compiler are recommended to:
 1. not expose flatbuffer generated code as part of their public APIs