diff --git a/accepted/0000-hub-online-synchronization.md b/accepted/0000-hub-online-synchronization.md
index 5b0d96e2..48d9db58 100644
--- a/accepted/0000-hub-online-synchronization.md
+++ b/accepted/0000-hub-online-synchronization.md
@@ -68,7 +68,7 @@ In the first stage the focus will be synchronizing software channels, since it's
 
 We will need a mechanism to create the channels in the peripheral servers (vendor and customs ones) in the desired organization. Those channels need to have as content source the corresponding HUB server repository URL, with the correct authentication token. With this, repo-sync will take care of channel synchronization (proof of concept already tested).
 
-POS:
+Pros:
 - Automatically update channel during the night with repo-sync/mgr-sync
 - No need to have specific code adaptations in case of schema changes. It will be handled any way in repo-sync changes
 - Rely on a stable specification: repositories metadata