Change intro

files/en-us/web/http/session/index.md

@@ -18,7 +18,7 @@ As of HTTP/1.1, the connection is no longer closed after completing the third ph
 
 In client-server protocols, it is the client which establishes the connection. Opening a connection in HTTP means initiating a connection in the underlying transport layer, usually this is TCP.
 
-With TCP the default port, for an HTTP server on a computer, is port 80. Other ports can also be used, like 8000 or 8080. The URL of a page to fetch contains both the domain name, and the port number, though the latter can be omitted if it is 80. See [Identifying resources on the Web](/en-US/docs/Web/URL) for more details.
+With TCP the default port, for an HTTP server on a computer, is port 80. Other ports can also be used, like 8000 or 8080. The URL of a page to fetch contains both the domain name, and the port number, though the latter can be omitted if it is 80. See [the URL reference](/en-US/docs/Web/URL) for more details.
 
 > [!NOTE]
 > The client-server model does not allow the server to send data to the client without an explicit request for it. However, various Web APIs enable this use case, including the [Push API](/en-US/docs/Web/API/Push_API), [Server-sent events](/en-US/docs/Web/API/Server-sent_events), and the [WebSockets API](/en-US/docs/Web/API/WebSockets_API).
@@ -156,7 +156,7 @@ X-Cache: Error from cloudfront
 
 ## See also
 
-- [Identifying resources on the Web](/en-US/docs/Web/URL)
+- [URLs](/en-US/docs/Web/URL)
 - [HTTP headers](/en-US/docs/Web/HTTP/Headers)
 - [HTTP request methods](/en-US/docs/Web/HTTP/Methods)
 - [HTTP response status codes](/en-US/docs/Web/HTTP/Status)

files/en-us/web/url/index.md

@@ -7,7 +7,7 @@ spec-urls: https://httpwg.org/specs/rfc9110.html#uri
 
 {{QuickLinksWithSubpages("/en-US/docs/Web/URL")}}
 
-The target of an HTTP request is called a "resource", whose nature isn't defined further; it can be a document, a photo, or anything else. Each resource is identified by a Uniform Resource Identifier ({{Glossary("URI")}}) used throughout HTTP for identifying resources.
+**URLs** are used to identify "resources" on the web. URLs are commonly used as targets of [HTTP](/en-US/docs/Web/HTTP) requests, in which case the URL represents a location for a physical resource, such as a document, a photo, binary data, etc. URLs can also be used to trigger behaviors other than fetching a resource, including opening the email client, sending text messages, or executing JavaScript, when used in other places such as the [`href`](/en-US/docs/Web/HTML/Element/a#href) of an HTML `<a>` link.
 
 ## URLs and URNs
 

files/en-us/web/url/resource_urls/index.md

@@ -32,7 +32,7 @@ loaded the next one:
 resource://<File-loader> -> <File-loaded>
 ```
 
-Please refer to [Identifying resources on the web](/en-US/docs/Web/URL) for more general details.
+Please refer to [the URL reference](/en-US/docs/Web/URL) for more general details.
 
 In this article, we focus on resource URIs, which are used internally by Firefox to
 point to built-in resources.
@@ -94,6 +94,6 @@ resource: is Firefox only.
 
 ## See also
 
-- [Identifying resources on the Web](/en-US/docs/Web/URL)
+- [URLs](/en-US/docs/Web/URL)
 - [What is a URL?](/en-US/docs/Learn/Common_questions/Web_mechanics/What_is_a_URL)
 - [IANA list of URI schemes](https://www.iana.org/assignments/uri-schemes/uri-schemes.xhtml) (`resource:` is [covered here](https://www.iana.org/assignments/uri-schemes/prov/resource))