diff --git a/lib/rubocop/cop/obsession/no_paragraphs.rb b/lib/rubocop/cop/obsession/no_paragraphs.rb
index 742a155..ba6c26b 100644
--- a/lib/rubocop/cop/obsession/no_paragraphs.rb
+++ b/lib/rubocop/cop/obsession/no_paragraphs.rb
@@ -8,7 +8,7 @@ module Obsession
       # If your method code has many instructions that are not organized into
       # paragraphs, you should break it up into multiple paragraphs to make the
       # code more breathable and readable. The 3 possible paragraphs themes
-      # always are: initialization, action, and result.
+      # could be: initialization, action, and result.
       #
       # @example
       #
diff --git a/lib/rubocop/cop/obsession/too_many_paragraphs.rb b/lib/rubocop/cop/obsession/too_many_paragraphs.rb
index 51a6221..797c1e7 100644
--- a/lib/rubocop/cop/obsession/too_many_paragraphs.rb
+++ b/lib/rubocop/cop/obsession/too_many_paragraphs.rb
@@ -6,13 +6,13 @@ module Obsession
       # This cop checks for methods with too many paragraphs.
       #
       # You should organize your method code into 2 to 3 paragraphs maximum.
-      # The 3 possible paragraphs themes always are: initialization, action,
+      # The 3 possible paragraphs themes could be: initialization, action,
       # and result. Shape your paragraph according to those themes. Spec code
       # should also be organized into 2 to 3 paragraphs
       # (initialization/action/result or given/when/then paragraphs).
       #
-      # After organizing your paragraphs, if they are too long or dense, it is
-      # a sign that you should break your code into smaller methods.
+      # After organizing your paragraphs, if they are too long or dense, it
+      # could be a sign that they should be broken into smaller methods.
       #
       # @example
       #