You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@teaclave.apache.org by ms...@apache.org on 2023/02/08 02:19:45 UTC

[incubator-teaclave] branch master updated: [docs] Fix typo (#675)

This is an automated email from the ASF dual-hosted git repository.

mssun pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-teaclave.git


The following commit(s) were added to refs/heads/master by this push:
     new 3b0e20e5 [docs] Fix typo (#675)
3b0e20e5 is described below

commit 3b0e20e57fe01a38721b61837698b82b4a36fff9
Author: Weijie Liu <ya...@antgroup.com>
AuthorDate: Wed Feb 8 10:19:39 2023 +0800

    [docs] Fix typo (#675)
---
 docs/mutual-attestation.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/mutual-attestation.md b/docs/mutual-attestation.md
index 0bee9df6..dc678047 100644
--- a/docs/mutual-attestation.md
+++ b/docs/mutual-attestation.md
@@ -33,7 +33,7 @@ other, it is impossible to decide which enclave is to be built first.
 
 Teaclave resolves this problem by relying on third-party auditors. We assume
 that there will be several parties trusted by all participants of Teaclave's
-computation tasks (could platforms, data providers, and customers, etc). The
+computation tasks (cloud platforms, data providers, and customers, etc). The
 source code and binaries of Teaclave are audited by these trusted parties. Once
 the auditors decided that Teaclave is secure, they sign and publish the
 identities of audited enclaves. The *public keys* of the auditors are


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@teaclave.apache.org
For additional commands, e-mail: commits-help@teaclave.apache.org