You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
More correctly, it should come at the end of the path part. It should come _before_ any query string (starts with a question mark `?`), and before any hash / fragment part (starts with a hash character `#`), if either of those is present.
11
+
More correctly, it should come at the end of the _path_ partof the URL.
12
12
13
-
Example before a query string
13
+
If a query string or hash/fragment is present in the URL, the trailing slash should come before those, as shown in these examples:
@@ -49,7 +51,7 @@ URL casing is somewhat inconsistent across the website. Guidelines for new reso
49
51
50
52
### A case exception: reference pages
51
53
52
-
In reference pages, the URLs follow the names of the functions, classes, and variables. So they include some capitals and use camel-case (`createCanvas`, not `create-canvas`).
54
+
In reference pages, the URLs follow the names of the functions, classes, and variables. So, they include some capitals and use "camel-case" e.g. `createCanvas`.
0 commit comments