Refresh sync.proto.

chrome/browser/sync/protocol/encryption.proto

Index: chrome/browser/sync/protocol/encryption.proto
diff --git a/chrome/browser/sync/protocol/encryption.proto b/chrome/browser/sync/protocol/encryption.proto
index 1a331f4cd47cbf6ee567f8c8aa87a62758e3dd70..89aba01b2c0167b3d5bb050cee319f85081a77e9 100644
--- a/chrome/browser/sync/protocol/encryption.proto
+++ b/chrome/browser/sync/protocol/encryption.proto
@@ -21,9 +21,10 @@ package sync_pb;
 // change their passphrase (and thus their encryption key) at any time. When
 // that happens, we make a best effort to reencrypt all nodes with the new
 // passphrase, but since we don't have transactions on the server-side, we
-// cannot garantee that every node will be reencrypted. As a workaround, we keep
-// track of all keys, assign each key a name (by using that key to encrypt a
-// well known string) and keep track of which key was used to encrypt each node.
+// cannot guarantee that every node will be reencrypted. As a workaround, we
+// keep track of all keys, assign each key a name (by using that key to encrypt
+// a well known string) and keep track of which key was used to encrypt each
+// node.
 message EncryptedData {
   optional string key_name = 1;
   optional string blob = 2;