From 6ae2a2b9f220ad8b9d0b5f82edce53d4bd9d214b Mon Sep 17 00:00:00 2001
From: wstgbot <62450690+wstgbot@users.noreply.github.com>
Date: Fri, 7 Nov 2025 17:44:43 +0000
Subject: [PATCH] Publish Latest 2025-11-07

Updates based on OWASP/wstg@4a4a3f6
---
 latest/5-Reporting/01-Reporting_Structure.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/latest/5-Reporting/01-Reporting_Structure.md b/latest/5-Reporting/01-Reporting_Structure.md
index a4bbf80c..569aa58a 100644
--- a/latest/5-Reporting/01-Reporting_Structure.md
+++ b/latest/5-Reporting/01-Reporting_Structure.md
@@ -13,7 +13,7 @@ Performing the technical side of the assessment is only half of the overall asse
 
 ## About This Section
 
-This guide provides only suggestions about one possible approach to reporting, and should not be treated as as strict rules that must be followed. When considering any of the recommendations below, always ask yourself whether the recommendation would improve your report.
+This guide provides only suggestions about one possible approach to reporting, and should not be treated as strict rules that must be followed. When considering any of the recommendations below, always ask yourself whether the recommendation would improve your report.
 
 This guide to reporting is a best fit for consultancy-based reports. It may be overkill for internal or bug bounty reports.