Clarify expectations of false positives/negatives (#27964)
Clarify expectations of false positives/negatives (#27964)

Today this part of the documentation just says that Geo queries are not 100% 
accurate, but in fact we can be more precise about which kinds of queries see
which kinds of error. This commit clarifies this point.

rajanm/elasticsearch,GlenRSmith/elasticsearch,rajanm/elasticsearch,HonzaKral/elasticsearch,gingerwizard/elasticsearch,robin13/elasticsearch,coding0011/elasticsearch,rajanm/elasticsearch,HonzaKral/elasticsearch,scorpionvicky/elasticsearch,uschindler/elasticsearch,gfyoung/elasticsearch,gingerwizard/elasticsearch,gfyoung/elasticsearch,GlenRSmith/elasticsearch,scorpionvicky/elasticsearch,nknize/elasticsearch,gingerwizard/elasticsearch,coding0011/elasticsearch,uschindler/elasticsearch,rajanm/elasticsearch,uschindler/elasticsearch,GlenRSmith/elasticsearch,robin13/elasticsearch,gingerwizard/elasticsearch,coding0011/elasticsearch,GlenRSmith/elasticsearch,HonzaKral/elasticsearch,coding0011/elasticsearch,nknize/elasticsearch,gingerwizard/elasticsearch,rajanm/elasticsearch,HonzaKral/elasticsearch,gingerwizard/elasticsearch,nknize/elasticsearch,scorpionvicky/elasticsearch,robin13/elasticsearch,nknize/elasticsearch,robin13/elasticsearch,rajanm/elasticsearch,gingerwizard/elasticsearch,uschindler/elasticsearch,gfyoung/elasticsearch,GlenRSmith/elasticsearch,nknize/elasticsearch,robin13/elasticsearch,uschindler/elasticsearch,coding0011/elasticsearch,gfyoung/elasticsearch,scorpionvicky/elasticsearch,scorpionvicky/elasticsearch,gfyoung/elasticsearch