diff --git a/client/src/main.rs b/client/src/main.rs
index e9252de..18e98dd 100644
--- a/client/src/main.rs
+++ b/client/src/main.rs
@@ -15,7 +15,7 @@
 //! * [images]: Container for viewing and interacting with media item previews
 //!
 //! * [image_overlay]: Overlay for viewing one high resolution media item at a time and browsing items sequentially
-//! (e.g. a lightbox)
+//!   (e.g. a lightbox)
 //!
 //! Additionally, there is the [client] module, which provides an API for communicating with the Tagger server.
 //!
@@ -236,10 +236,10 @@ pub struct State {
 /// This will do all of the following:
 ///
 /// * Attempt to authenticate with the Tagger server (which is assumed to be the same as the host from which the
-/// app was loaded)
+///   app was loaded)
 ///
 /// * Instantiate and wire up the reactive state for this app, using the "hash" portion of the URI to decode
-/// routing state, if present
+///   routing state, if present
 ///
 /// * Bind handlers for global keyboard events
 ///
diff --git a/client/src/tag_menu.rs b/client/src/tag_menu.rs
index a10ea55..7262df6 100644
--- a/client/src/tag_menu.rs
+++ b/client/src/tag_menu.rs
@@ -30,9 +30,9 @@ pub enum List<T> {
 /// For example, if the current filter is "year:2017 and state:hawaii", and some of the matching items also have
 /// tags like "city:honolulu" and "city:kailua-kona", then "city" would be one of the categories we'd return here,
 /// but "year" and "state" would not be since we're already filtering by those categories.
-fn find_categories<'a>(
+fn find_categories(
     filter_chain: &List<Tag>,
-    categories: &'a HashMap<Arc<str>, TagsResponse>,
+    categories: &HashMap<Arc<str>, TagsResponse>,
     result: &mut Vec<Arc<str>>,
 ) {
     for (category, tags) in categories {