"HTTP connection scope" is somewhat misleading

[nggit]

Each incoming HTTP request is treated independently, with a new scope created for every request, even if they originate from the same client and reuse the same TCP connection (e.g., with HTTP/1.1 keep-alive).

Thus, the term "HTTP connection scope" can be misleading, as people might interpret it as HTTP persistent connection.

Wouldn't "HTTP request scope" or "HTTP transaction scope" be a more accurate term?