Corrected usage of "it's" in stout. Review: https://reviews.apache.org/r/52831/
Project: http://git-wip-us.apache.org/repos/asf/mesos/repo Commit: http://git-wip-us.apache.org/repos/asf/mesos/commit/124f6e38 Tree: http://git-wip-us.apache.org/repos/asf/mesos/tree/124f6e38 Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/124f6e38 Branch: refs/heads/master Commit: 124f6e38914b0949405b5ef127e0c4fb145c8c1f Parents: 5fb8220 Author: Neil Conway <neil.con...@gmail.com> Authored: Thu Oct 13 16:16:39 2016 -0700 Committer: Joseph Wu <josep...@apache.org> Committed: Thu Oct 13 17:36:47 2016 -0700 ---------------------------------------------------------------------- 3rdparty/stout/README.md | 2 +- 3rdparty/stout/include/stout/os/linux.hpp | 2 +- 3rdparty/stout/include/stout/os/posix/killtree.hpp | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/mesos/blob/124f6e38/3rdparty/stout/README.md ---------------------------------------------------------------------- diff --git a/3rdparty/stout/README.md b/3rdparty/stout/README.md index 172150c..693e3a3 100644 --- a/3rdparty/stout/README.md +++ b/3rdparty/stout/README.md @@ -565,7 +565,7 @@ Converts arbitrary types into strings by attempting to use an overloaded `std::o *Requires pthreads.* -You can give every thread it's own copy of some data using the `ThreadLocal` abstraction: +You can give every thread its own copy of some data using the `ThreadLocal` abstraction: ~~~{.cpp} ThreadLocal<std::string> local; http://git-wip-us.apache.org/repos/asf/mesos/blob/124f6e38/3rdparty/stout/include/stout/os/linux.hpp ---------------------------------------------------------------------- diff --git a/3rdparty/stout/include/stout/os/linux.hpp b/3rdparty/stout/include/stout/os/linux.hpp index fd9b0ed..bf12e0b 100644 --- a/3rdparty/stout/include/stout/os/linux.hpp +++ b/3rdparty/stout/include/stout/os/linux.hpp @@ -92,7 +92,7 @@ inline pid_t clone( // (1) Failed to clone. // // (2) CLONE_VM is not set implying ::clone will create a process - // which runs in it's own copy of the memory space of the + // which runs in its own copy of the memory space of the // calling process. If CLONE_VM is set ::clone will create a // thread which runs in the same memory space with the calling // process, in which case we don't want to call delete! http://git-wip-us.apache.org/repos/asf/mesos/blob/124f6e38/3rdparty/stout/include/stout/os/posix/killtree.hpp ---------------------------------------------------------------------- diff --git a/3rdparty/stout/include/stout/os/posix/killtree.hpp b/3rdparty/stout/include/stout/os/posix/killtree.hpp index 8ba21de..f47f0d8 100644 --- a/3rdparty/stout/include/stout/os/posix/killtree.hpp +++ b/3rdparty/stout/include/stout/os/posix/killtree.hpp @@ -195,7 +195,7 @@ inline Try<std::list<ProcessTree>> killtree( } // There is a concern that even though some process is stopped, - // sending a signal to any of it's children may cause a SIGCLD to + // sending a signal to any of its children may cause a SIGCLD to // be delivered to it which wakes it up (or any other signal maybe // delivered). However, from the Open Group standards on "Signal // Concepts":
