Merge branch 'pritianka-master-patch-68826' into 'master'

Update source/handbook/general-guidelines/index.html.md

See merge request gitlab-com/www-gitlab-com!23190

source/handbook/general-guidelines/index.html.md

@@ -71,7 +71,7 @@ Most things are **public** unless there is a reason not to. Not public by defaul
 1. Customer information is not public since customers are not comfortable with that and it would make it easier for competitors to approach our customers.
 1. [Sales battlecards](https://blog.pandadoc.com/the-basics-of-battle-cards/) are not public since we want to minimize the time the competition has to respond to it. Our [feature comparisons](https://about.gitlab.com/devops-tools/) are public.
 1. When we discuss a customer by name that is not public unless we're sure the customer is OK with that. When we discuss a competitor (for example in a sales call) this can be public as our competitive advantages are public.
-1. Reorganizations are not public and on a need to know basis even within the organization. Reorganizations cause disruption and they tend to change a lot before being decided upon, so being public about them prolongs the disruption.
+1. Plans for reorganizations are not public and on a need-to-know basis within the organization. Reorganizations cause disruption and the plans tend to change a lot before being finalized, so being public about them prolongs the disruption. We will keep relevant team-members informed whenever possible.
 ## Be transparent
 1. Work out in the **open**, try to use public issue trackers and repositories when possible.