for prelude-admin :

--- libprelude-3.1.0/docs/manpages/prelude-admin.1      2016-09-15 02:49:10.736000884 -0400
+++ libprelude-3.1.0/docs/manpages/prelude-admin.1      2017-03-16 17:18:37.724295826 -0400
@@ -26,11 +26,11 @@
  - Creating directory to be used by the agent (example: failover purpose)
  - Registering to a remote 'prelude-manager': get a signed X509 certificate that will allow communication between agent and manager using the specified permissions.

-All these informations are stored in an agent profile.
+All these information are stored in an agent profile.

 An agent profile is identified by its name. When an agent is started, it will load the profile of the same name as the program itself, that is, if your agent is named "prelude-lml", the agent will load the profile named "prelude-lml".

-The name of the profile can be overriden using the '--prelude --profile name_of_my_profile' command line option. It is possible to define the profile name so that you can have several instances of one agent running with different permissions, using different profiles.
+The name of the profile can be overridden using the '--prelude --profile name_of_my_profile' command line option. It is possible to define the profile name so that you can have several instances of one agent running with different permissions, using different profiles.

 Note that profiles are not specific to agents, but are used in all programs of the Prelude suite (agents, managers, etc).