chore: fix some typos in comments (#1090)

Signed-off-by: luohewuyang <[email protected]>

Author: luohewuyang

data-url/src/mime.rs

@@ -95,7 +95,7 @@ fn parse_parameters(s: &str, parameters: &mut Vec<(String, String)>) {
         let piece = piece.trim_start_matches(http_whitespace);
         let (name, value) = split2(piece, '=');
         // We can not early return on an invalid name here, because the value
-        // parsing later may consume more semicolon seperated pieces.
+        // parsing later may consume more semicolon separated pieces.
         let name_valid =
             !name.is_empty() && only_http_token_code_points(name) && !contains(parameters, name);
         if let Some(value) = value {

debug_metadata/README.md

@@ -18,7 +18,7 @@ The GNU debugger (GDB) supports defining custom debugger views using Pretty Prin
 Pretty printers are written as python scripts that describe how a type should be displayed
 when loaded up in GDB/LLDB. (See: https://sourceware.org/gdb/onlinedocs/gdb/Pretty-Printing.html#Pretty-Printing)
 The pretty printers provide patterns, which match type names, and for matching
-types, descibe how to display those types. (For writing a pretty printer, see: https://sourceware.org/gdb/onlinedocs/gdb/Writing-a-Pretty_002dPrinter.html#Writing-a-Pretty_002dPrinter).
+types, describe how to display those types. (For writing a pretty printer, see: https://sourceware.org/gdb/onlinedocs/gdb/Writing-a-Pretty_002dPrinter.html#Writing-a-Pretty_002dPrinter).
 
 ### Embedding Visualizers
 

url/src/lib.rs

@@ -2746,7 +2746,7 @@ impl Url {
                     str_len.saturating_sub(scheme_diff + 2)
                 }
             } else if cfg!(windows) {
-                // remove scheme: - has posssible \\ for hostname
+                // remove scheme: - has possible \\ for hostname
                 str_len.saturating_sub(self.scheme().len() + 1)
             } else {
                 // remove scheme://