From 951aa3ae215cdffbd6eab0a9b4e65cdf2c3f05ff Mon Sep 17 00:00:00 2001 From: Nico Schottelius Date: Wed, 1 Dec 2010 20:13:29 +0100 Subject: [PATCH] --typos Signed-off-by: Nico Schottelius --- blog/what-is-configuration-management.mdwn | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/blog/what-is-configuration-management.mdwn b/blog/what-is-configuration-management.mdwn index 3c9881fd..8d623158 100644 --- a/blog/what-is-configuration-management.mdwn +++ b/blog/what-is-configuration-management.mdwn @@ -54,7 +54,7 @@ the user understand, nor do I know why I did it. Yes, it can get even worse, there may be managers or bosses around, who pay the poor sysadmin. The sysadmin claims to do -her best job, but as a manager, I don't understand what he's +her best job, but as a manager, I don't understand what she's doing. Nor do I really care. I care about the users (which could be customers as well!) and that their demands. And about how many users and how many demands my sysadmin @@ -69,7 +69,7 @@ brainstorming, there are some outcomes: * CM must be easy to use, so the lazy sysadmin will use it * CM includes ideas from users - * The implementation is done by the sysadmin + * The configuration management is maintained by the sysadmin * Your managers are happy, if the CM outputs "manager readable data" ## More stuff