From d85e1afd7e8172e0ddfdaaf0c434319f6b6f3099 Mon Sep 17 00:00:00 2001 From: Lirusaito Date: Sun, 5 Feb 2012 18:18:22 -0500 Subject: [PATCH] Spelling fix to documentation. --- indra/llcommon/llfasttimer_class.cpp | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/indra/llcommon/llfasttimer_class.cpp b/indra/llcommon/llfasttimer_class.cpp index 83c5b4fc1..15075aa87 100644 --- a/indra/llcommon/llfasttimer_class.cpp +++ b/indra/llcommon/llfasttimer_class.cpp @@ -27,7 +27,7 @@ // // LLFastTimer documentation, written by Aleric (Feb 2012). // -// Disclaimer: this is horrible code and I distantiate myself from it's design. +// Disclaimer: this is horrible code and I distantiate myself from its design. // It's neither robust nor object oriented. I just document what I find, in // order to be able to fix the bugs (that logically result from such a design). // @@ -63,12 +63,12 @@ // LLFastTimer::getFrameStateList()[named_timer.getFrameStateIndex()], where // getFrameStateList() is a static function returning a global std::vector. // This vector is ordered "Depth First" (the FrameState objects (belonging to -// NamedTimer objects) with smallest depth first). The vector is resorted a few +// NamedTimer objects) with smallest depth first). The vector is re-sorted a few // times in the beginning (and indexes in FrameState updated) since timers are added // whenever they are first used, not in "Depth First" order, but stabilizes after a // while. This implies that FrameState pointers can't really be used: FrameState // objects move around in memory whenever something is inserted or removed from the -// std::vector and/or when the vector is resorted. However, FrameState pointers ARE +// std::vector and/or when the vector is re-sorted. However, FrameState pointers ARE // being used and code exists that tries to update those pointers in the above // mentioned cases (this part had bugs, which I now fixed). //