"The setter method for a property should use the form setPropertyName:. For a property called firstName, the setter method should be called setFirstName:; for a Boolean property called paused, the setter method should be called setPaused:."

It's true, the document doesn't say that it's exclusive to setters, that's on me.

Just like you don't want to use ["get"](http://stackoverflow.com/questions/20859819/ios-arc-application-and-one-line-or-two-initializations-of-objects#comment31295121_20859819) when defining a method name, you generally want to avoid using "set" unless you are overriding a setter. 

Of course, if you do something like what was in the example, `-(void)setString:(NSString *)someString withImage:(UIImage *)someImage`, there's no way that could override a setter but for the sake of clarity, when I see a method that starts with "set", I generally know that it's overriding a setter otherwise it's a custom method I made to do something. 

Ultimately, this is a style issue but one I try to keep in my own code to differentiate the methods that are overriding synthesized property methods as opposed to code I'm responsible for.