| Index: chrome/browser/chromeos/drive/search_metadata.h
|
| diff --git a/chrome/browser/chromeos/drive/search_metadata.h b/chrome/browser/chromeos/drive/search_metadata.h
|
| index 2012f01cefb19dc606ac11efe3caf62961c6aa8d..59e62edd8964f59bf5c4add9aaedd92a79d8100b 100644
|
| --- a/chrome/browser/chromeos/drive/search_metadata.h
|
| +++ b/chrome/browser/chromeos/drive/search_metadata.h
|
| @@ -27,7 +27,7 @@ struct MetadataSearchResult {
|
| DriveEntryProto entry_proto;
|
|
|
| // The base name to be displayed in the UI. The parts matched the search
|
| - // query are highlited with <b> tag. Meta characters are escaped like <
|
| + // query are highlighted with <b> tag. Meta characters are escaped like <
|
| //
|
| // Why HTML? we could instead provide matched ranges using pairs of
|
| // integers, but this is fragile as we'll eventually converting strings
|
|
|