@@ -104,8 +104,8 @@ use sys::path::{is_sep_byte, is_verbatim_sep, MAIN_SEP_STR, parse_prefix};
104
104
/// Windows uses a variety of path prefix styles, including references to drive
105
105
/// volumes (like `C:`), network shared folders (like `\\server\share`), and
106
106
/// others. In addition, some path prefixes are "verbatim" (i.e. prefixed with
107
- /// `\\?\`, in which case `/` is *not* treated as a separator and essentially no
108
- /// normalization is performed.
107
+ /// `\\?\`) , in which case `/` is *not* treated as a separator and essentially
108
+ /// no normalization is performed.
109
109
///
110
110
/// # Examples
111
111
///
@@ -510,7 +510,7 @@ pub enum Component<'a> {
510
510
511
511
/// The root directory component, appears after any prefix and before anything else.
512
512
///
513
- /// It represents a deperator that designates that a path starts from root.
513
+ /// It represents a separator that designates that a path starts from root.
514
514
#[ stable( feature = "rust1" , since = "1.0.0" ) ]
515
515
RootDir ,
516
516
@@ -1965,7 +1965,7 @@ impl Path {
1965
1965
///
1966
1966
/// When parsing the path, there is a small amount of normalization:
1967
1967
///
1968
- /// * Repeated seperators are ignored, so `a/b` and `a//b` both have
1968
+ /// * Repeated separators are ignored, so `a/b` and `a//b` both have
1969
1969
/// `a` and `b` as components.
1970
1970
///
1971
1971
/// * Occurentces of `.` are normalized away, exept if they are at the
0 commit comments