[Radar] Address hyperlint issues

Author: meddulla

src/content/docs/radar/investigate/url-scanner.mdx

@@ -77,13 +77,13 @@ While the scan is in progress, the HTTP status code will be `404`, once it's fin
 The response will include, among others, the following top properties:
 
 * `task` - Information on the scan submission.
-* `page` - Information pertaining to the primary response (e.g. ip address, ASN, server and page redirect history).
+* `page` - Information pertaining to the primary response, for example IP address, ASN, server and page redirect history.
 * `data.requests` - Request chains involved in the page load.
 * `data.cookies` - Cookies set by the page.
 * `data.globals` - Non-standard JavaScript global variables.
 * `data.console` - Console logs.
 * `data.performance` - Timings as given by the [`PerformanceNavigationTiming`](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceNavigationTiming) interface.
-* `meta` - Meta processors output including detected technologies, domain and url categories, rank, geoip information and others.
+* `meta` - Meta processors output including detected technologies, domain and URL categories, rank, geoip information and others.
 * `lists.ips` - IPs contacted.
 * `lists.asns` - AS Numbers contacted.
 * `lists.domains` - Hostnames contacted, including `dns` record information.
@@ -94,7 +94,7 @@ The response will include, among others, the following top properties:
 Some examples of more specific properties include:
 
 * `task.uuid` - ID of the scan.
-* `task.url` - Submitted url of the scan. May differ from final url (`page.url`) if there HTTP redirects.
+* `task.url` - Submitted URL of the scan. May differ from final URL (`page.url`) if there are HTTP redirects.
 * `task.success` - Whether scan was successful or not. Scans can fail for various reasons, including DNS errors.
 * `task.status` - Current scan status, for example, `Queued`, `InProgress`, or `Finished`.
 * `meta.processors.domainCategories` - Cloudflare categories of the main hostname contacted.
@@ -134,8 +134,8 @@ curl "https://api.cloudflare.com/client/v4/accounts/{account_id}/urlscanner/v2/s
 
 Some other example queries:
 
-- `task.url:"https://google.com" OR task.url:"https://www.google.com"` - search for scans whose submitted url was either `google.com` or `www.google.com`. URLs *must* be enclosed in quotes.
-- `page.url:"https://google.com" AND NOT task.url:"https://google.com"` - search for scans to `google.com` whose submitted url was not `google.com` (ie. sites that redirected to google.com)
+- `task.url:"https://google.com" OR task.url:"https://www.google.com"` - search for scans whose submitted URL was either `google.com` or `www.google.com`. URLs *must* be enclosed in quotes.
+- `page.url:"https://google.com" AND NOT task.url:"https://google.com"` - search for scans to `google.com` whose submitted url was not `google.com` (that is, sites that redirected to google.com)
 - `page.domain:microsoft AND verdicts.malicious:true AND NOT page.domain:microsoft.com`: malicious scans whose hostname starts with "microsoft". Would match domains like "microsoft.phish.com"
 - `apikey:me AND date:[2024-01 TO 2024-10]`: my scans from 2024 January to 2024 October.
 - `page.domain:(blogspot OR www.blogspot)`: Searches for scans whose main domain starts with `blogspot` or with `www.blogspot`