diff --git a/indra/llfilesystem/lldiskcache.cpp b/indra/llfilesystem/lldiskcache.cpp
index dd7d1a043ff..ea33178a1e9 100644
--- a/indra/llfilesystem/lldiskcache.cpp
+++ b/indra/llfilesystem/lldiskcache.cpp
@@ -64,9 +64,9 @@ LLDiskCache::LLDiskCache(const std::string& cache_dir,
 // WARNING: purge() is called by LLPurgeDiskCacheThread. As such it must
 // NOT touch any LLDiskCache data without introducing and locking a mutex!
 
-// Interaction through the filesystem itself should be safe. Let’s say thread
+// Interaction through the filesystem itself should be safe. Let's say thread
 // A is accessing the cache file for reading/writing and thread B is trimming
-// the cache. Let’s also assume using llifstream to open a file and
+// the cache. Let's also assume using llifstream to open a file and
 // boost::filesystem::remove are not atomic (which will be pretty much the
 // case).
 
diff --git a/indra/llkdu/llimagej2ckdu.cpp b/indra/llkdu/llimagej2ckdu.cpp
index e7ac6bdb31e..5d2927d9746 100644
--- a/indra/llkdu/llimagej2ckdu.cpp
+++ b/indra/llkdu/llimagej2ckdu.cpp
@@ -228,11 +228,11 @@ struct LLKDUMessageError : public LLKDUMessage
     {
         // According to the documentation nat found:
         // http://pirlwww.lpl.arizona.edu/resources/guide/software/Kakadu/html_pages/globals__kdu$mize_errors.html
-        // "If a kdu_error object is destroyed, handler→flush will be called with
+        // "If a kdu_error object is destroyed, handler->flush will be called with
         // an end_of_message argument equal to true and the process will
         // subsequently be terminated through exit. The termination may be
         // avoided, however, by throwing an exception from within the message
-        // terminating handler→flush call."
+        // terminating handler->flush call."
         // So throwing an exception here isn't arbitrary: we MUST throw an
         // exception if we want to recover from a KDU error.
         // Because this confused me: the above quote specifically refers to