Fix typo in README (#507)

* fix typo in README

* Fix OpenEnclave/Open Enclave typo elsewhere

* OpenEnOpen

Author: letmaik

README.md

@@ -48,8 +48,8 @@ transactions in highly performant and highly available fashion.
 
 ## A flexible confidentiality layer for any multi-party computation application or blockchain ledger to build upon
 
-CCF currently runs on [Intel SGX](https://software.intel.com/en-us/sgx)-enabled platforms. Because CCF uses the [OpenEnclave SDK](https://github.com/openenclave/openenclave)
-as the foundation for running in an enclave, as OpenEnclave supports new TEE technologies, CCF will be able to run on new platforms. Networks can be run on-premises,
+CCF currently runs on [Intel SGX](https://software.intel.com/en-us/sgx)-enabled platforms. Because CCF uses the [Open Enclave SDK](https://github.com/openenclave/openenclave)
+as the foundation for running in an enclave, as Open Enclave supports new TEE technologies, CCF will be able to run on new platforms. Networks can be run on-premises,
 in one or many cloud-hosted data centers, including [Microsoft Azure](https://azure.microsoft.com/), or in any hybrid configuration.
 
 Ledger providers can use CCF to enable higher throughput and higher confidentiality guarantees for distributed ledger applications.

getting_started/setup_vm/roles/openenclave/tasks/install.yml

@@ -1,37 +1,37 @@
 - name: Include vars
   include_vars: common.yml
 
-- name: Download OpenEnclave source
+- name: Download Open Enclave source
   get_url:
     url: "{{ oe_url }}"
     dest: "{{ workspace }}/{{ oe_src }}"
     force: yes
   become: true
 
-- name: Remove Pre-existing OpenEnclave source on the remote
+- name: Remove Pre-existing Open Enclave source on the remote
   file:
     path: "{{ workspace }}/openenclave-{{ oe_ver }}"
     state: absent
 
-- name: Create directory for OpenEnclave source
+- name: Create directory for Open Enclave source
   file:
     path: "{{ workspace }}/openenclave-{{ oe_ver }}"
     state: directory
 
-- name: Expand OpenEnclave
+- name: Expand Open Enclave
   unarchive:
     src: "{{ workspace }}/{{ oe_src }}"
     dest: "{{ workspace }}/openenclave-{{ oe_ver }}"
     copy: no
     extra_opts: [--strip-components=1]
     creates: "{{ workspace }}/openenclave-{{ oe_ver }}/CMakeLists.txt"
 
-- name: Make OpenEnclave build dir
+- name: Make Open Enclave build dir
   file:
     path: "{{ workspace }}/openenclave-{{ oe_ver }}/build"
     state: directory
 
-# OpenEnclave turns on the Clang speculative load hardening pass by default.
+# Open Enclave turns on the Clang speculative load hardening pass by default.
 # This is good practice for arbitrary enclaved code, as it applies a general
 # mitigation that does not depend on source code annotation. However, being
 # a general mitigation, it also carries about a 30% performance penalty when
@@ -45,7 +45,7 @@
     regexp: '-mllvm -x86-speculative-load-hardening'
     replace: ''
 
-- name: Install OpenEnclave dependencies
+- name: Install Open Enclave dependencies
   shell: |
     scripts/ansible/install-ansible.sh
     ansible-playbook "{{ oe_playbook }}"
@@ -60,12 +60,12 @@
     name: ninja-build
   become: true
 
-- name: Make OpenEnclave build dir
+- name: Make Open Enclave build dir
   file:
     path: "{{ workspace }}/openenclave-{{ oe_ver }}/build"
     state: directory
 
-- name: Build OpenEnclave
+- name: Build Open Enclave
   shell: |
     cmake -GNinja -DCMAKE_INSTALL_PREFIX:PATH={{ oe_prefix }} -DCMAKE_BUILD_TYPE=RelWithDebInfo {{ oe_build_opts }} ..
     ninja
@@ -74,13 +74,13 @@
   async: 600
   poll: 5
 
-- name: Remove Pre-existing OpenEnclave install
+- name: Remove Pre-existing Open Enclave install
   file:
     path: "{{ oe_prefix }}"
     state: absent
   become: true
 
-- name: Install OpenEnclave
+- name: Install Open Enclave
   command: ninja install
   args:
     chdir: "{{ workspace }}/openenclave-{{ oe_ver }}/build"

sphinx/source/glossary.rst

@@ -24,14 +24,14 @@ Glossary
   Microsoft Azure
     `Microsoft Azure <https://azure.microsoft.com>`_ is a cloud computing service created by Microsoft for building, testing, deploying, and managing applications and services through Microsoft-managed data centers.
 
-  OpenEnclave
-    `OpenEnclave SDK <https://openenclave.io/sdk>`_ is an SDK for building enclave applications in C and C++.
+  Open Enclave
+    `Open Enclave SDK <https://openenclave.io/sdk>`_ is an SDK for building enclave applications in C and C++.
 
   Operators
     Are in charge of operating a CCF network (e.g. adding or removing nodes). Their identities are not registered in CCF.
 
-  OpenEnclave Engine
-    `OpenEnclave Engine <https://github.com/Microsoft/oe-engine>`_ is a template generation tool for :term:`Azure Confidential Compute`.
+  Open Enclave Engine
+    `Open Enclave Engine <https://github.com/Microsoft/oe-engine>`_ is a template generation tool for :term:`Azure Confidential Compute`.
 
   Quorum
     A quorum of members is defined as the minimum number of members required to accept governance proposals. It is defined by the governance as a Lua script set when a CCF network is created.

sphinx/source/introduction.rst

@@ -48,8 +48,8 @@ transactions in highly performant and highly available fashion.
 A flexible confidentiality layer for multi-party computation
 ------------------------------------------------------------
 
-CCF currently runs on Intel :term:`SGX`-enabled platforms. Because CCF uses the :term:`OpenEnclave` SDK
-as the foundation for running in an enclave, as :term:`OpenEnclave` supports new TEE technologies, CCF will be able to run on new platforms. Networks can be run on-premises,
+CCF currently runs on Intel :term:`SGX`-enabled platforms. Because CCF uses the :term:`Open Enclave` SDK
+as the foundation for running in an enclave, as :term:`Open Enclave` supports new TEE technologies, CCF will be able to run on new platforms. Networks can be run on-premises,
 in one or many cloud-hosted data centers, including :term:`Microsoft Azure`, or in any hybrid configuration.
 
 Ledger providers can use CCF to enable higher throughput and higher confidentiality guarantees for distributed ledger applications.

sphinx/source/members/common_member_operations.rst

@@ -34,7 +34,7 @@ If the version of the code being executed needs to be updated (for example, to s
 
     $ memberclient --cert member_cert --privk member_privk --rpc-address node_ip:node_port --ca network_cert add_code --new-code-id code_version
 
-.. note:: For a given :term:`OpenEnclave` enclave library, the version of the code (``mrenclave``) can be found by running the ``oesign`` utility:
+.. note:: For a given :term:`Open Enclave` enclave library, the version of the code (``mrenclave``) can be found by running the ``oesign`` utility:
 
     .. code-block:: bash
 

sphinx/source/quickstart/build.rst

@@ -46,7 +46,7 @@ The full list of build switches can be obtained by running:
 * **CLIENT_MBEDTLS_PREFIX**: Path. Prefix to mbedtls install to be used by test clients. Default to ``/usr/local``.
 * **SERVICE_IDENTITY_CURVE_CHOICE**: String, one of ``secp384r1``, ``curve25519``, ``secp256k1_mbedtls``, ``secp256k1_bitcoin``. Elliptic curve to use for CCF network and node identities. Defaults to ``secp384r1``.
 * **NO_STRICT_TLS_CIPHERSUITES**: Boolean. Relax the list of accepted TLS ciphersuites. Default to OFF.
-* **OE_PREFIX**: Path. OpenEnclave install prefix. Default to ``/opt/openenclave``.
+* **OE_PREFIX**: Path. Open Enclave install prefix. Default to ``/opt/openenclave``.
 * **SAN**: Boolean. Build unit tests with Address and Undefined behaviour sanitizers enabled. Default to OFF.
 * **TARGET**: String, one of ``all``, ``sgx``, ``virtual``. Defaults to ``all``, which builds both "virtual" enclaves and actual SGX enclaves.
 * **VERBOSE_LOGGING**: Boolean. Enable all logging levels. Default to OFF.

sphinx/source/quickstart/oeengine.rst

@@ -1,7 +1,7 @@
 OE Engine Walkthrough
 =====================
 
-:term:`OpenEnclave Engine` (OE Engine) offers detailed `deployment instructions`_, but this is a very condensed summary to get a CCF-ready VM up and running in 5 minutes. You can either execute these steps on a machine with the `Azure CLI`_ installed, or use `Azure Cloud Shell`_ (installed by the ``pre_make_vm.sh`` script).
+:term:`Open Enclave Engine` (OE Engine) offers detailed `deployment instructions`_, but this is a very condensed summary to get a CCF-ready VM up and running in 5 minutes. You can either execute these steps on a machine with the `Azure CLI`_ installed, or use `Azure Cloud Shell`_ (installed by the ``pre_make_vm.sh`` script).
 
 1. Download the `oe-engine binary`_ for your platform.
 2. Create a definition file as ``vm.json``:

sphinx/source/quickstart/requirements.rst

@@ -45,7 +45,7 @@ Azure Confidential Compute
 
 .. note:: These steps require an `Azure subscription <https://docs.microsoft.com/en-us/azure/billing/billing-create-subscription#create-a-subscription-in-the-azure-portal>`_.
 
-:term:`Azure Confidential Compute` (ACC) offers DC-series VMs using SGX hardware, which can be deployed either through a `Marketplace App`_, or through the :term:`OpenEnclave Engine`.
+:term:`Azure Confidential Compute` (ACC) offers DC-series VMs using SGX hardware, which can be deployed either through a `Marketplace App`_, or through the :term:`Open Enclave Engine`.
 
 .. note:: On Windows, you can use `WSL <https://docs.microsoft.com/en-us/windows/wsl/install-win10>`_ or `Azure Cloud Shell (Bash) <https://azure.microsoft.com/en-us/features/cloud-shell/>`_ to run the following commands.
 
@@ -55,7 +55,7 @@ First, from your local machine, you should clone the CCF repository to get acces
 
     $ git clone https://github.com/microsoft/CCF.git
 
-First, you should run the ``pre_make_vm.sh`` script to install the `Azure CLI`_ and the :term:`OpenEnclave Engine` (``oe-engine``) that are required to create the DC-series in Azure:
+First, you should run the ``pre_make_vm.sh`` script to install the `Azure CLI`_ and the :term:`Open Enclave Engine` (``oe-engine``) that are required to create the DC-series in Azure:
 
 .. code-block:: bash
 

src/enclave/oe_shim.h

@@ -16,7 +16,7 @@
 #else
 
 // Repeat or approximate a lot of OE definitions, so that the virtual library
-// can be compiled without any reference to OpenEnclave. This may need updating
+// can be compiled without any reference to Open Enclave. This may need updating
 // to stay up-to-date with OE.
 
 #  define OE_EXTERNC extern "C"