Tiny punctuation fix

documentation/pluggable-roster-support-guide.html

@@ -127,7 +127,7 @@ <h4>Should I include all the dependencies that my code needs?</h4>
         <h4>Isn't it easier to deploy my code as an Openfire plugin?</h4>
         <p>
             It is not recommended to use a plugin for packaging and deploying your provider. For one, plugins use a
-            dedicated class path. For another, the load order of plugins could lead to hairy scenario's, and finally:
+            dedicated class path. For another, the load order of plugins could lead to hairy scenarios, and finally:
             plugins can be <em>unloaded</em> at runtime. This all could lead to a running Openfire service for which you
             cannot guarantee that your provider is loaded at all times. For these reasons, we recommend creating a jar
             file instead of an Openfire plugin, and placing that jar file in Openfire's lib directory!