docs: change URL occurences to uppercase (#22151)

* change URL occurences to uppercase

* Update docs/sources/tutorials/iis.md

Co-Authored-By: Diana Payton <52059945+oddlittlebird@users.noreply.github.com>

Co-authored-by: Diana Payton <52059945+oddlittlebird@users.noreply.github.com>

docs/sources/http_api/dashboard.md

@@ -16,7 +16,7 @@ parent = "http_api"
 The identifier (id) of a dashboard is an auto-incrementing numeric value and is only unique per Grafana install.
 
 The unique identifier (uid) of a dashboard can be used for uniquely identify a dashboard between multiple Grafana installs.
-It's automatically generated if not provided when creating a dashboard. The uid allows having consistent URL's for accessing
+It's automatically generated if not provided when creating a dashboard. The uid allows having consistent URLs for accessing
 dashboards and when syncing dashboards between multiple Grafana installs, see [dashboard provisioning]({{< relref "../administration/provisioning.md#dashboards" >}})
 for more information. This means that changing the title of a dashboard will not break any bookmarked links to that dashboard.
 
@@ -284,7 +284,7 @@ Please note that these resource have been deprecated and will be removed in a fu
 
 `GET /api/dashboards/db/:slug`
 
-Will return the dashboard given the dashboard slug. Slug is the url friendly version of the dashboard title.
+Will return the dashboard given the dashboard slug. Slug is the URL friendly version of the dashboard title.
 If there exists multiple dashboards with the same slug, one of them will be returned in the response.
 
 **Example Request**:
@@ -332,7 +332,7 @@ Status Codes:
 
 `DELETE /api/dashboards/db/:slug`
 
-Will delete the dashboard given the specified slug. Slug is the url friendly version of the dashboard title.
+Will delete the dashboard given the specified slug. Slug is the URL friendly version of the dashboard title.
 
 **Example Request**:
 

docs/sources/http_api/folder.md

@@ -15,7 +15,7 @@ parent = "http_api"
 
 The identifier (id) of a folder is an auto-incrementing numeric value and is only unique per Grafana install.
 
-The unique identifier (uid) of a folder can be used for uniquely identify folders between multiple Grafana installs. It's automatically generated if not provided when creating a folder. The uid allows having consistent URL's for accessing folders and when syncing folders between multiple Grafana installs. This means that changing the title of a folder will not break any bookmarked links to that folder.
+The unique identifier (uid) of a folder can be used for uniquely identify folders between multiple Grafana installs. It's automatically generated if not provided when creating a folder. The uid allows having consistent URLs for accessing folders and when syncing folders between multiple Grafana installs. This means that changing the title of a folder will not break any bookmarked links to that folder.
 
 The uid can have a maximum length of 40 characters.
 

docs/sources/http_api/org.md

@@ -337,7 +337,7 @@ Accept: application/json
 Accept: application/json
 Content-Type: application/json
 ```
-Note: The api will only work when you pass the admin name and password
+Note: The api will only work when you pass the admin name and password
 to the request HTTP URL, like http://admin:admin@localhost:3000/api/orgs/1/users
 
 
@@ -417,7 +417,7 @@ Accept: application/json
 
 ```
 Note: The api will only work when you pass the admin name and password
-to the request HTTP url, like http://admin:admin@localhost:3000/api/orgs/1/users
+to the request HTTP URL, like http://admin:admin@localhost:3000/api/orgs/1/users
 
 
 **Example Response**:

docs/sources/http_api/team.md

@@ -34,7 +34,7 @@ Default value for the `perpage` parameter is `1000` and for the `page` parameter
 
 The `totalCount` field in the response can be used for pagination of the teams list E.g. if `totalCount` is equal to 100 teams and the `perpage` parameter is set to 10 then there are 10 pages of teams.
 
-The `query` parameter is optional and it will return results where the query value is contained in the `name` field. Query values with spaces need to be url encoded e.g. `query=my%20team`.
+The `query` parameter is optional and it will return results where the query value is contained in the `name` field. Query values with spaces need to be URL encoded e.g. `query=my%20team`.
 
 ### Using the name parameter
 

docs/sources/http_api/user.md

@@ -63,7 +63,7 @@ Content-Type: application/json
 
 `GET /api/users/:id`
 
-**Example Request**:
+**Example Request**:
 
 ```http
 GET /api/users/1 HTTP/1.1