Replace eg

docs/docs/examples/emojivoto.md

@@ -14,7 +14,7 @@ the voting and leader board logic (`voting`). The `vote-bot` simulates user traf
 votes to the frontend.
 
 Emojivoto can be seen as a lighthearted example of an app dealing with sensitive data.
-Contrast protects emojivoto in two ways. First, it shields emojivoto as a whole from the infrastructure e.g., Azure.
+Contrast protects emojivoto in two ways. First, it shields emojivoto as a whole from the infrastructure, for example, Azure.
 Second, it can be configured to also prevent data access even from the administrator of the app. In the case of emojivoto, this gives assurance to users that their votes remain secret.
 
 <!-- TODO(katexochen): recreate in our design -->
@@ -148,7 +148,7 @@ The public facing frontend for voting uses the mesh certificate without client a
 
 ## Verifying the deployment as a user
 
-In different scenarios, users of an app may want to verify its security and identity before sharing data, e.g., before casting a vote.
+In different scenarios, users of an app may want to verify its security and identity before sharing data, for example, before casting a vote.
 With Contrast, a user only needs a single remote-attestation step to verify the deployment - regardless of the size or scale of the deployment.
 Contrast is designed such that, by verifying the Coordinator, the user transitively verifies those systems the Coordinator has already verified or will verify in the future.
 Successful verification of the Coordinator means that the user can be sure that the given manifest will be enforced.