From eedac9c6c2a661a2d9ef0dd1a215f5ce76a96a07 Mon Sep 17 00:00:00 2001
From: Mathy Vanhoef <Mathy.Vanhoef@kuleuven.be>
Date: Thu, 15 Apr 2021 18:09:05 +0400
Subject: [PATCH] fragattacks: README: title and spelling fix

---
 research/README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/research/README.md b/research/README.md
index 4ff663f41..4c01edf4f 100644
--- a/research/README.md
+++ b/research/README.md
@@ -1,4 +1,4 @@
-# <div align="center">Fragmentation & Aggregation Attacks</div>
+# <div align="center">FragAttacks: Fragmentation & Aggregation Attacks</div>
 
 # 1. Introduction
 
@@ -754,7 +754,7 @@ only vulnerable while connecting to the network (i.e. during the execution of th
 
 <a id="id-extended-bcast-check-ping-bp"></a>
 
-- `ping BP [--bcast-dst]`: this is a variant of the above two tests, except that the ping request is now send in a
+- `ping BP [--bcast-dst]`: this is a variant of the above two tests, except that the ping request is now sent in a
   plaintext unicast frame instead of a broadcast one (no CVE is allocated yet - it's related to CVE-2020-26145). This test
   must be performed against both clients and APs. The ping is sent before the client has authenticated with the network
   (i.e. during the execution of the 4-way handshake), meaning you must run tcpdump or wireshark to check if the device