more consistent use of terminology; trait > syntax

diff --git a/clippy_lints/src/methods/mod.rs b/clippy_lints/src/methods/mod.rs
index 8e3a75f2c7b5605033c2080a7f6210a7d2237789..10e6644b70e1e8b6e622ad5022976b756210ff1a 100644 (file)
--- a/clippy_lints/src/methods/mod.rs
+++ b/clippy_lints/src/methods/mod.rs
@@ -569,13 +569,13 @@
 /// concise.
 ///
 /// **Known problems:** Not a replacement for error handling: Using either
-/// `.unwrap()` or the Index syntax (`[]`) carries the risk of causing a `panic`
+/// `.unwrap()` or the Index trait (`[]`) carries the risk of causing a `panic`
 /// if the value being accessed is `None`. If the use of `.get().unwrap()` is a
 /// temporary placeholder for dealing with the `Option` type, then this does
 /// not mitigate the need for error handling. If there is a chance that `.get()`
 /// will be `None` in your program, then it is advisable that the `None` case
-/// is eventually handled in a future refactor instead of using `.unwrap()`
-/// or the Index syntax.
+/// is handled in a future refactor instead of using `.unwrap()` or the Index 
+/// trait.
 ///
 /// **Example:**
 /// ```rust