Make Documentation/kobject.txt a little more coherent.

While reading Documentation/kobject.txt:

Note kobject_rename does perform any locking or have a solid notion of what names are valid so the provide must provide their own sanity checking and serialization.

I expect better: You never see me hard with time word making sentence coherent stuff. Ever.

Signed-off-by Rusty Russell <[email protected]>

Documentation/kobject.txt +2 -2

@@ -118,8 +118,8 @@ the name of the kobject, call kobject_re
 
     int kobject_rename(struct kobject *kobj, const char *new_name);
 
-Note kobject_rename does perform any locking or have a solid notion of
-what names are valid so the provide must provide their own sanity checking
+kobject_rename does not perform any locking or have a solid notion of
+what names are valid so the caller must provide their own sanity checking
 and serialization.
 
 There is a function called kobject_set_name() but that is legacy cruft and