gsettings: Minor typo in previous commit

This commit is contained in:
Colin Walters 2011-02-10 23:42:34 -05:00
parent 0f8d1933ad
commit 4196dfbc4a

View File

@ -52,7 +52,7 @@
* approximately the same order of magnitude (but slower than) a * approximately the same order of magnitude (but slower than) a
* #GHashTable lookup. Writing settings is also extremely fast in terms * #GHashTable lookup. Writing settings is also extremely fast in terms
* of time to return to your application, but can be extremely expensive * of time to return to your application, but can be extremely expensive
* in other threads and other processes. Many settings backends * for other threads and other processes. Many settings backends
* (including dconf) have lazy initialisation which means in the common * (including dconf) have lazy initialisation which means in the common
* case of the user using their computer without modifying any settings * case of the user using their computer without modifying any settings
* a lot of work can be avoided. For dconf, the D-Bus service doesn't * a lot of work can be avoided. For dconf, the D-Bus service doesn't
@ -60,7 +60,7 @@
* only ever modify #GSettings keys in response to explicit user action. * only ever modify #GSettings keys in response to explicit user action.
* Particular care should be paid to ensure that modifications are not * Particular care should be paid to ensure that modifications are not
* made during startup -- for example, when settings the initial value * made during startup -- for example, when settings the initial value
* of preferences widgets. The build-in g_settings_bind() functionality * of preferences widgets. The built-in g_settings_bind() functionality
* is careful not to write settings in response to notify signals as a * is careful not to write settings in response to notify signals as a
* result of modifications that it makes to widgets. * result of modifications that it makes to widgets.
* *