Cleanup typos in routes docs

I should really use spellcheck more often
This commit is contained in:
Emi Tatsuo 2020-11-20 23:51:22 -05:00
parent 536e404fdf
commit cd7af1025a
Signed by: Emi
GPG Key ID: 68FAB2E2E6DFC98B
2 changed files with 3 additions and 3 deletions

View File

@ -33,7 +33,7 @@ impl<T> RoutingNode<T> {
/// should be represented as `&["dir", "image.png"]`. /// should be represented as `&["dir", "image.png"]`.
/// ///
/// If a match is found, it is returned, along with the segments of the path trailing /// If a match is found, it is returned, along with the segments of the path trailing
/// the subpath matcing the route. For example, a route `/foo` recieving a request to /// the subpath matching the route. For example, a route `/foo` receiving a request to
/// `/foo/bar` would produce `vec!["bar"]` /// `/foo/bar` would produce `vec!["bar"]`
/// ///
/// See [`RoutingNode`] for details on how routes are matched. /// See [`RoutingNode`] for details on how routes are matched.

View File

@ -55,7 +55,7 @@ impl Request {
/// ///
/// If the trailing segments have not been set, this method will panic, but this /// If the trailing segments have not been set, this method will panic, but this
/// should only be possible if you are constructing the Request yourself. Requests /// should only be possible if you are constructing the Request yourself. Requests
/// to handlers registered through [`add_route`](northstar::Builder::add_route()) will /// to handlers registered through [`add_route`](crate::Builder::add_route()) will
/// always have trailing segments set. /// always have trailing segments set.
pub fn trailing_segments(&self) -> &Vec<String> { pub fn trailing_segments(&self) -> &Vec<String> {
self.trailing_segments.as_ref().unwrap() self.trailing_segments.as_ref().unwrap()
@ -64,7 +64,7 @@ impl Request {
/// All of the segments in this path, percent decoded /// All of the segments in this path, percent decoded
/// ///
/// For example, for a request to `/api/v1/endpoint`, this would return `["api", "v1", /// For example, for a request to `/api/v1/endpoint`, this would return `["api", "v1",
/// "endpoint"]`, no matter what route the handler that recieved this request was /// "endpoint"]`, no matter what route the handler that received this request was
/// bound to. This is not to be confused with /// bound to. This is not to be confused with
/// [`trailing_segments()`](Self::trailing_segments), which contains only the segments /// [`trailing_segments()`](Self::trailing_segments), which contains only the segments
/// following the bound route. /// following the bound route.