| 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 9cb7bebe711892d66e9f451de48d0e559dfdfda0..8e13e1175b87f23568557000f53119288887b843 100644
|
| --- a/chrome/browser/chromeos/drive/search_metadata.h
|
| +++ b/chrome/browser/chromeos/drive/search_metadata.h
|
| @@ -27,12 +27,12 @@ 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
|
| // from UTF-8 (StringValue in base/values.h uses std::string) to UTF-16
|
| - // when sending strings from C++ to JavaSCript.
|
| + // when sending strings from C++ to JavaScript.
|
| //
|
| // Why <b> instead of <strong>? Because <b> is shorter.
|
| std::string highlighted_base_name;
|
|
|