(DOCSP-11402): Remove repetition in Don't Humanize Inanimate Objects (#66)

* (DOCSP-11402): Remove repetition in Don't Humanize Inanimate Objects

* copy review

* Update source/style-guide/writing/use-effective-verbs.txt

Co-authored-by: Anthony Sansone <[email protected]>

Co-authored-by: Anthony Sansone <[email protected]>

Author: melissamahoney-mongodb

source/style-guide/writing/use-effective-verbs.txt

@@ -336,11 +336,12 @@ Be careful not to ascribe human feelings, motivations, and actions to
 inanimate objects. For example, a web application doesn't *know*,
 *need*, *remember*, *see*, *think*, *understand*, or *want*.
 
-Be careful not to ascribe human qualities, traits, or emotions to
-inanimate objects like software, hardware, or interfaces. Often, we use
-anthropomorphic words in an attempt to make difficult topics more understandable or relatable. This can actually make the
-concept harder to grasp for ESL readers or those less familiar with
-metaphors.
+Often, we humanize technology with anthropomorphic words.
+Some writers believe this makes difficult topics more
+understandable or relatable. These words can make the
+concept harder to grasp for:
+- Readers that are less familiar with metaphors.
+- Readers with English as a second language.
 
 There are standard anthropomorphic verbs in the computer industry. For
 example, a software program can detect, record, require, store, check,