Merge pull request #297 from askervin/559_fpga_plugin_doc_orchestrated

fpga_plugin: orchestration/orchestrated fixed in READMEs

Author: mythi

cmd/fpga_admissionwebhook/README.md

@@ -36,9 +36,9 @@ shown in the following table:
 
 | FPGA plugin mode | matching admission controller mode |
 |:---------------- |:---------------------------------- |
-| region           | orchestration                      |
+| region           | orchestrated                       |
 | af               | preprogrammed                      |
- 
+
 
 # Dependencies
 
@@ -140,7 +140,7 @@ $ ./scripts/webhook-deploy.sh --ca-bundle-path /var/run/kubernetes/server-ca.crt
 Requested FPGA resources are translated to AF resources. For example,
 `fpga.intel.com/arria10.dcp1.1-nlb0` is translated to `fpga.intel.com/af-d8424dc4a4a3c413f89e433683f9040b`.
 
-In orchestration mode, `fpga.intel.com/arria10.dcp1.1-nlb0` gets translated to
+In orchestrated mode, `fpga.intel.com/arria10.dcp1.1-nlb0` gets translated to
 `fpga.intel.com/region-9926ab6d6c925a68aabca7d84c545738`, and, the corresponding AF IDs are set in
 environment variables for the container. The [FPGA CRI-O hook](../fpga_crihook/README.md)
 then loads the requested bitstream to a region before the container is started.

cmd/fpga_plugin/README.md

@@ -75,7 +75,7 @@ development, initial deployment and debugging.
 
 The FPGA plugin set can run in one of two modes:
 
-- `region`/`orchestration` mode, where the plugins locate and advertise
+- `region`/`orchestrated` mode, where the plugins locate and advertise
   regions of the FPGA, and facilitate programing of those regions with the
   requested bistreams.
 - `af`/`preprogrammed` mode, where the FPGA bitstreams are already loaded
@@ -318,4 +318,3 @@ device-plugin registered
 # Next steps
 
 Continue installation with the [FPGA admission controller webhook](../fpga_admissionwebhook/README.md).
-