diff options
| author | Cai Yuanqing <ckjacket@gmail.com> | 2011-01-25 00:20:34 +0800 |
|---|---|---|
| committer | Sebastian Dröge <sebastian.droege@collabora.co.uk> | 2011-01-24 19:52:30 +0100 |
| commit | eea239f47caa206b4bfdd879433fdbd018136cd2 (patch) | |
| tree | 0a5ad407f2596b9dbcc2054cfe36370b352e5ccf | |
| parent | 3d858ccc18ef5c62df86f7c64c743544f53e82a9 (diff) | |
design docs: fix 2 typos in part-MT-refcounting
| -rw-r--r-- | docs/design/part-MT-refcounting.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/design/part-MT-refcounting.txt b/docs/design/part-MT-refcounting.txt index a6e652935..888607231 100644 --- a/docs/design/part-MT-refcounting.txt +++ b/docs/design/part-MT-refcounting.txt @@ -55,7 +55,7 @@ Shared data structures and writability: The advantage of this method is that no reader/writers locks are needed. all threads can concurrently read but writes happen locally on a new copy. In most cases _get_writable() can avoid a real copy because the calling method is the - only one holding a reference, wich makes read/writes very cheap. + only one holding a reference, which makes read/write very cheap. The drawback is that sometimes 1 needless copy can be done. This would happen when N threads call _get_writable() at the same time, all seeing that N @@ -193,7 +193,7 @@ Objects disposed it has to unset itself as the parent of the object before disposing itself, else the child object holds a parent pointer to invalid memory. - The responsibilites for an object that sinks other objects are summarised as: + The responsibilities for an object that sinks other objects are summarised as: - taking ownership of the object - call _object_set_parent() to set itself as the object parent, this call |