Replace "it's" with "its" in several places.

src/ripple/app/paths/README.md

@@ -21,7 +21,7 @@ This is the **rippled** implementation; there are many other possible implementa
  * When searching, limit our search to the rippled cache.
 2. Six degrees of separation.
  * If sending value through individual's account, expect no path to have more than six hops.
- * According to [Facebook studies](https://www.facebook.com/notes/facebook-data-team/anatomy-of-facebook/10150388519243859) as of late 2011, it's users are separated by fewer than five steps.
+ * According to [Facebook studies](https://www.facebook.com/notes/facebook-data-team/anatomy-of-facebook/10150388519243859) as of late 2011, its users are separated by fewer than five steps.
  * By using XRP for bridging the most complicated path expected is usually:
  * source -> gateway -> XRP -> gateway -> destination
 3. Pareto principle.
@@ -135,8 +135,3 @@ If you can compute a path already yourself or know one, you don't need to do ste
  * very little time, can't afford to do a search.
  * that's why we do the path building before the payment is due.
  * The routine used to compute liquidity and ledger change is also called RippleCalc::rippleCalc.
-
-
-
-
-

src/ripple/core/impl/JobQueue.cpp

@@ -424,8 +424,8 @@ private:
     // Post-conditions:
     //  job is a valid Job object.
     //  job is removed from mJobQueue.
-    //  Waiting job count of it's type is decremented
-    //  Running job count of it's type is incremented
+    //  Waiting job count of its type is decremented
+    //  Running job count of its type is incremented
     //
     // Invariants:
     //  The calling thread owns the JobLock

src/ripple/peerfinder/sim/WrappedSink.h

@@ -23,7 +23,7 @@
 namespace ripple {
 namespace PeerFinder {
 
-/** Wraps a Journal::Sink to prefix it's output. */
+/** Wraps a Journal::Sink to prefix its output. */
 class WrappedSink : public beast::Journal::Sink
 {
 public:

src/ripple/protocol/tests/STObject.test.cpp

@@ -60,7 +60,7 @@ public:
             arrays/objects.
 
             STObject is an associative container, mapping fields to value, but
-            an STObject may also have a Field as it's name, stored outside the
+            an STObject may also have a Field as its name, stored outside the
             associative structure. The name is important, so to maintain
             fidelity, it will take TWO json objects to represent them.