There seem to be number of problems with the text as currently presented

Using the URL/address bar to enter the web address or IP address of a website

The IP address is a web address. It's just a numerical one that bypasses the DNS (but may cause things to break if the server doesn't receive a Host header that it's expecting) --Ianhcooper (talk) 00:10, 13 August 2013 (PDT)

Using the search box in a search engine/browser to search for a website

I know you're mozilla but this sets an expectation of an awesome bar. Search seems to have been shoehorned into an aspect that's related to underlying technologies (URLs, DNS names, IP addresses) because in some browsers the same dialogue element allows for search. --Ianhcooper (talk) 00:10, 13 August 2013 (PDT)

Explaining how DNS resolves URLs to IP addresses

This is completely wrong. A URL has a hostname element that is resolved by the DNS (if not in the local hosts file) to an IP address which is used by the underlying TCP connection. The DNS isn't used for the remainder of the URL, which is sent to the server at the resolved hostname for resolution. --Ianhcooper (talk) 00:10, 13 August 2013 (PDT)

Do you perhaps mean something along the lines of "Explaining how DNS is used by the browser to find a website from a URL" --Ianhcooper (talk) 00:10, 13 August 2013 (PDT)

Missing?

Port numbers / hostname trust

You seem to have missed any reference to port numbers and the relative "lack of trust" for any http connection to a port number other than 80, or an https connection other than to port 443. Further, that reference to "secure" in a hostname in itself doesn't mean that the connection would be secure. I couldn't easily find anything about "checking for secure connections" elsewhere. --Ianhcooper (talk) 00:10, 13 August 2013 (PDT)

My error, you touch on secure connections on another page: Recognising the visual cues --Ianhcooper (talk) 01:09, 13 August 2013 (PDT)