chore(AIP-185): clarify in-place change language (#1565)

Author: tlinkowski

aip/general/0185.md

@@ -24,8 +24,8 @@ Note: The use of the term "major version number" above is taken from
 [semantic versioning][]. However, unlike in traditional semantic versioning,
 Google APIs **must not** expose minor or patch version numbers. For
 example, Google APIs use `v1`, not `v1.0`, `v1.1`, or `v1.4.2`. From a user's
-perspective, major versions are updated in place, and users receive new
-functionality without migration.
+perspective, major versions are updated in place with minor/patch equivalent
+changes, and users receive new functionality without migration.
 
 A new major version of an API **must not** depend on a previous major version of
 the same API. An API surface **must not** depend on other APIs, except for in