aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorTim D. Smith2016-09-06 20:15:32 -0700
committerGitHub2016-09-06 20:15:32 -0700
commitadaba7157dfb5ef51f3e8798c26645f010b0a4de (patch)
tree3c1c7c907cf2dbc230a4076aebd94b8a125fc064
parent069d5f00bc90875dad89da3ec786709632fed6e1 (diff)
parenta1145a88b200d611ba4cd37981dc68fa7b288012 (diff)
downloadbrew-adaba7157dfb5ef51f3e8798c26645f010b0a4de.tar.bz2
Merge pull request #885 from numbergames/patch-2
minor typo
-rw-r--r--share/doc/homebrew/Analytics.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/share/doc/homebrew/Analytics.md b/share/doc/homebrew/Analytics.md
index 3f663f588..1346e767b 100644
--- a/share/doc/homebrew/Analytics.md
+++ b/share/doc/homebrew/Analytics.md
@@ -32,7 +32,7 @@ It is impossible for the Homebrew developers to match any particular event to an
![Aggregate user analytics](images/analytics.png)
-As far as we can tell it would be impossible Google to match the randomly generated Homebrew-only analytics user ID to any other Google Analytics user ID. If Google turned evil the only thing they could do would be to lie about anonymising IP addresses and attempt to match users based on IP addresses.
+As far as we can tell it would be impossible for Google to match the randomly generated Homebrew-only analytics user ID to any other Google Analytics user ID. If Google turned evil the only thing they could do would be to lie about anonymising IP addresses and attempt to match users based on IP addresses.
## When/Where?
Homebrew's analytics are sent throughout Homebrew's execution to Google Analytics over HTTPS.