possessives

docs/ThreadTheft.md

@@ -34,7 +34,7 @@ To *avoid* this, we use the
 on whether you have a `SynchronizationContext`. If you *don't* (common for console applications,
 services, etc), then the TPL uses the standard thread-pool mechanisms to schedule the
 continuation. If you *do* have a `SynchronizationContext` (common in UI applications
-and web-servers), then it's `Post` method is used instead; the `Post` method is *meant* to
+and web-servers), then its `Post` method is used instead; the `Post` method is *meant* to
 be an asynchronous dispatch API. But... not all impementations are equal. Some 
 `SynchronizationContext` implementations treat `Post` as a synchronous invoke. This is true
 in particular of `LegacyAspNetSynchronizationContext`, which is what you get if you