From c420f448b3cc8b6cd0c0f6c7f71b1544df8a8f9f Mon Sep 17 00:00:00 2001 From: Alex Gaynor Date: Sun, 29 Jun 2014 11:11:03 -0700 Subject: [PATCH] Wrap two code examples in backticks This makes the docs ever-so-slightly easier to read. --- src/libstd/path/mod.rs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/libstd/path/mod.rs b/src/libstd/path/mod.rs index e55dc165895..6d48122b186 100644 --- a/src/libstd/path/mod.rs +++ b/src/libstd/path/mod.rs @@ -35,8 +35,8 @@ code, `Path` should be used to refer to the platform-native path. Creation of a path is typically done with either `Path::new(some_str)` or `Path::new(some_vec)`. This path can be modified with `.push()` and `.pop()` (and other setters). The resulting Path can either be passed to another -API that expects a path, or can be turned into a &[u8] with `.as_vec()` or a -Option<&str> with `.as_str()`. Similarly, attributes of the path can be queried +API that expects a path, or can be turned into a `&[u8]` with `.as_vec()` or a +`Option<&str>` with `.as_str()`. Similarly, attributes of the path can be queried with methods such as `.filename()`. There are also methods that return a new path instead of modifying the receiver, such as `.join()` or `.dir_path()`.