[incubator-teaclave] branch master updated: Fix some typos (#340)

[ms...@apache.org]

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 40fed0c  Fix some typos (#340)
40fed0c is described below

commit 40fed0cd25dd01c563290d053d7f824da7e2e67f
Author: Qinkun Bao <qi...@gmail.com>
AuthorDate: Fri Jun 5 18:29:01 2020 -0400

    Fix some typos (#340)
---
 file_agent/README.md | 2 +-
 rpc/README.md        | 2 +-
 services/README.md   | 8 ++++----
 tests/README.md      | 6 +++---
 4 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/file_agent/README.md b/file_agent/README.md
index a288eb2..6408f8f 100644
--- a/file_agent/README.md
+++ b/file_agent/README.md
@@ -9,7 +9,7 @@ handle file downloading/uploading from and to various storage service providers
 (e.g., AWS S3).
 
 Before executing a task, the execution service will use the file agent to
-prepare any registered input files comes with the task. For example, the
+prepare any registered input files that come with the task. For example, the
 registered file input could be a presigned URL from AWS S3. The file agent will
 download and prepare the file in local. With these files in the local storage,
 the executor can finally invoke the function. Similarly, after the task is
diff --git a/rpc/README.md b/rpc/README.md
index aa03e90..1439f90 100644
--- a/rpc/README.md
+++ b/rpc/README.md
@@ -37,7 +37,7 @@ and attestation configs.
 
 ## Protocol
 
-There are many RPC protocols can be implemented in the RPC framework. Currently,
+There are many RPC protocols that can be implemented in the RPC framework. Currently,
 there's only one simple protocol called `JsonProtocol`. Simply speaking, for
 the json protocol, one RPC message will contain a length of the following
 requests (in big endian) and a json serialized request.
diff --git a/services/README.md b/services/README.md
index 0578500..f00a732 100644
--- a/services/README.md
+++ b/services/README.md
@@ -26,13 +26,13 @@ a safe and secure FaaS platform.
   and function information will be persistent into the storage services.
 - **Storage Service**: Basically, the storage service stores persistent data like
   function, execution data, and task information in the platform. Here, we
-  deploy a key-value database (an implementation of LevelDB) in TEE and use
+  deploy a key-value database (an implementation of LevelDB) in TEE and use the
   protected file system (secured by the enclave) for data persistence.
 - **Access Control Service**: Provides a flexible access control domain specific
-  language to support access control rules for multi-party secure computation.
+  language to support access control rules for secure multi-party computation.
   The access control engine is written in Python and evaluated in SGX. Please
   read [this document](../docs/access-control.md) to learn more about the design of it.
-- **Scheduler Service**: Schedules staged task ready for execution to a proper
+- **Scheduler Service**: Schedules staged tasks ready for execution to a proper
   execution node with desirable capabilities.
 - **Execution Service**: A host of different executors interacting with the
   scheduler service to complete tasks. There could be many execution service
@@ -67,6 +67,6 @@ clients => frontend ----------> management            scheduler <-- execution
 ```
 
 Internal endpoint connections will be established and verified with mutual
-remote attestation to ensure the integrity and confidentiality of whole system.
+remote attestation to ensure the integrity and confidentiality of the whole system.
 Therefore, clients can trust the whole platform and safely interacting with the
 system through the attested authentication and frontend services.
diff --git a/tests/README.md b/tests/README.md
index e39b03f..c641e86 100644
--- a/tests/README.md
+++ b/tests/README.md
@@ -33,18 +33,18 @@ To generate a coverage report for tests, you can configure cmake with
 
 - `unit`:
   Unit tests are small and more focused, testing one module in isolation at a
-  time, and can test private interfaces. This directory contains test driver to
+  time, and can test private interfaces. This directory contains a test driver to
   test individual units/components or private interfaces. Test cases of unit
   tests are placed along with source code.
 - `integration`:
   Integration tests are entirely external to libraries, using only the public
   interface and potentially exercising multiple modules per test. This directory
-  contains test driver and tests cases to test public interfaces in common
+  contains a test driver and test cases to test public interfaces in common
   libraries.
 - `functional`:
   Functional testing is a type of black-box testing. In Teaclave, the test cases
   are usually sent through RPC channel.
-  This directory contains test driver and tests cases for Teaclave services. To
+  This directory contains a test driver and test cases for Teaclave services. To
   run these tests, services need to be launched.
 - `fixtures`:
   Testing fixtures are some files and sample inputs/outputs for testing only.


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