Should flag "amount of size"

I came across this redundancy yesterday or today and hunted for more examples:

Mistakes to flag and/or correct:
- This would still process the entire HTTP request, but would limit the **amount of size** a single request could buffer to disk.
- Instead, I want to trade for an **amount of size** that is equivalent to 100 in cash for every trade.
- If I remember correctly (but it's been years since I looked at it), "-g" added huge **amount of size** to the debug builds, due to ASAN, ...
- What I wanted to do: combine wikipedia files to one, but in place because I don't have that much **amount of size**.
- This is probably because in addition to the data within the disk, there is a minimum **amount of size** required for file system structures.
- significant **amount of size** and randomness to make them sufficiently hard to guess or iterate.
- Note that by necessity this job will persistently consume your available storage quota in the **amount of size** of git-svn clone * number of retained builds
- ... **amount of size** in bytes taken up by hardware morph textures.
- Reports the **amount of size** in bytes taken up by hardware morph textures.
- Determining real **amount of size** used in directory with hard links
- I need if function to count **amount of size** from column in C and D automatically.
- I am trying to change the default behavior of log4j to stop writing log entries to a file when the log file reaches certain **amount of size**.
- which would add a huge **amount of size** and weight to the laptop.
- Double the amount of hardware resources typically means double the **amount of size** and performance.
- Equal steps in scale do not add the same **amount of size**
- I've got 3 files in my Linux system that logs informations in /var/log/ and tend to get big for the **amount of size** I have available.
- It derives its name from when someone has faced a problem and someone who is constrained by a given **amount of size** of knapsack and it must fill it with the ...
- ... **amount of size** or RAM wastage and something that could be flexible or possibly able to increase and decrease the memory it's gathering based ...
- WebP Image format can save incredible **amount of size** if you have many images in your app.
- So that it does not depend on the **amount of size** of the node "rectangle"?
- I think it is related to the **amount of size** I allocate for the db and log.

Potential false positives:
- It's impossible for this API to exist and not leak some **amount of size** information.
- How to calculate the unique **amount of size** pairs for a given range of width and height?
- Some **amount of size** bloat is also acceptable

Hard to classify:
- ... significant **amount of size** difference after loading two exact same dump files

No file or test is named. Start by locating the existing grammar rules and tests for phrase-level redundancy, then review how ambiguous matches are handled. Done means the clear examples are flagged or corrected without triggering the listed false positives and hard-to-classify example.

Written by the indexing model from the issue text.