about summary refs log tree commit diff
diff options
context:
space:
mode:
authorMatthias Krüger <matthias.krueger@famsik.de>2022-07-23 12:08:14 +0200
committerGitHub <noreply@github.com>2022-07-23 12:08:14 +0200
commit7c5df1f425ef87c0f8c6bfc44df28ec0d6cc4fca (patch)
tree86e1e86dbc3cd77c3bfcf0efa5b4686f7ff079e4
parentf510d98ad387f2da7be0ad137ef2a9fd80dc812e (diff)
parentdb977ca37ed2adff2d3b04e2af10d0776f2e5aef (diff)
Rollup merge of #99632 - danbev:locator.rs-typo, r=Dylan-DPC
Fix typo/grammar in locator.rs doc comment
-rw-r--r--compiler/rustc_metadata/src/locator.rs2
1 files changed, 1 insertions, 1 deletions
diff --git a/compiler/rustc_metadata/src/locator.rs b/compiler/rustc_metadata/src/locator.rs
index a72bcb9a2db..2c1c84b0be2 100644
--- a/compiler/rustc_metadata/src/locator.rs
+++ b/compiler/rustc_metadata/src/locator.rs
@@ -67,7 +67,7 @@
 //!
 //! ## What criterion to select on?
 //!
-//! This a pretty tricky area of loading crates. Given a file, how do we know
+//! This is a pretty tricky area of loading crates. Given a file, how do we know
 //! whether it's the right crate? Currently, the rules look along these lines:
 //!
 //! 1. Does the filename match an rlib/dylib pattern? That is to say, does the