From c0c388d861f576731c6ee9e004c89fe75279bc0c Mon Sep 17 00:00:00 2001
From: q1800 <95879668+q1800@users.noreply.github.com>
Date: Sun, 10 Apr 2022 12:34:52 -0500
Subject: [PATCH] Undo previous correction from web page -> webpage

---
 Contributed-memory-usage:-benchmarks-over-time.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/Contributed-memory-usage:-benchmarks-over-time.md b/Contributed-memory-usage:-benchmarks-over-time.md
index 9639759..90d6e26 100644
--- a/Contributed-memory-usage:-benchmarks-over-time.md
+++ b/Contributed-memory-usage:-benchmarks-over-time.md
@@ -1,8 +1,8 @@
-This page is just a place for me to keep track of contributed memory to web pages over time. I consider the contributed memory to webpages to be more important than the own memory footprint. Unfortunately, a user can not see how much memory overhead an extension contributes to a webpage without running a benchmark like the one here. Keep in mind the results here are only for **one basic web page.**
+This page is just a place for me to keep track of contributed memory to web pages over time. I consider the contributed memory to web pages to be more important than the own memory footprint. Unfortunately, a user can not see how much memory overhead an extension contributes to a web page without running a benchmark like the one here. Keep in mind the results here are only for **one basic web page.**
 
-Using [Acid Test 3](http://acid3.acidtests.org/), a simple webpage with embedded `iframes`, the webpage opened in a new tab for each extension after a browser restart.
+Using [Acid Test 3](http://acid3.acidtests.org/), a simple web page with embedded `iframes`, the web page opened in a new tab for each extension after a browser restart.
 
-Each extension was tested alone, with no other extensions enabled. Leaving the browser idle for more than 1 minute ensured that the webpage memory was garbage collected.
+Each extension was tested alone, with no other extensions enabled. Leaving the browser idle for more than 1 minute ensured that the web page memory was garbage collected.
 
 Added the following steps for benchmarks dated December 2014 and later:
 
@@ -21,7 +21,7 @@ I found that this was now necessary as it appears the Chromium garbage collector
 - Adblock Plus (ABP) 1.8.8 (_EasyList_, _EasyPrivacy_, _Malware Protection List_, _"Acceptable ads"_ disabled)
 
 Summary of results:
-- Reference memory usage for the webpage: 23 MB
+- Reference memory usage for the web page: 23 MB
 - uBO adds over 10 MB
 - ABP adds over 33 MB
 - ABP with the same filter lists as uBO adds over 46 MB
@@ -45,7 +45,7 @@ ABP with same filter lists as uBO:<br>
 - ABP 1.8.5 (_EasyList_, _EasyPrivacy_, _Malware Protection List_, _"Acceptable ads"_ disabled)
 
 Summary of results:
-- Reference memory usage for the webpage: 22 MB
+- Reference memory usage for the web page: 22 MB
 - uBO Plus adds over 9 MB
 - ABP adds over 32 MB
 
@@ -60,4 +60,4 @@ ABP:<br>
 
 Observations:
 
-The last time I ran this benchmark [was on Chromium 34 64-bit](./%C2%B5Block-vs.-ABP:-efficiency-compared#added-memory-footprint-to-web-pages), and it does appear that Chromium 37 is causing webpages to consume more memory. The reference result went from ~17 MB to ~22 MB.
+The last time I ran this benchmark [was on Chromium 34 64-bit](./%C2%B5Block-vs.-ABP:-efficiency-compared#added-memory-footprint-to-web-pages), and it does appear that Chromium 37 is causing web pages to consume more memory. The reference result went from ~17 MB to ~22 MB.