odh-23178-4 feature store - more peer review edits (#895)

Author: MelissaFlinn

assemblies/customizing-your-feature-store-configuration.adoc

@@ -16,7 +16,7 @@ Optionally, you can apply the following configurations to your Feature Store ins
 
 The examples in the following sections describe how to customize a Feature Store instance by creating a new custom resource definition (CRD). Alternatively, you can customize an existing feature instance as described in _Editing an existing Feature Store instance_.
 
-For more information about how you can customize your feature store configuration, see the 
+For more information about how you can customize your Feature Store configuration, see the 
 link:https://github.com/feast-dev/feast/blob/stable/infra/feast-operator/docs/api/markdown/ref.md[Feast API documentation^].
 
 

modules/configuring-role-based-access-control.adoc

@@ -16,15 +16,15 @@ The RBAC implementation in Feature Store is designed to provide the following ca
 
 Feature Store RBAC provides the following benefits:
 
-* *Feature sharing* - Enable multiple teams to share the feature store while ensuring controlled access. This capability allows for collaborative work without compromising data security.
+* *Feature sharing* - Enable multiple teams to share a Feature Store instance while ensuring controlled access. This capability allows for collaborative work without compromising data security.
 * *Access control management* - Prevent unauthorized access to team-specific resources and spaces, governing the operations that each user or group can perform.
 
-The Feature Store permissions model allows you to configure granular permission policies to all the resources defined in a feature store.
+The Feature Store permissions model allows you to configure granular permission policies to all the resources defined in a Feature Store instance.
 
 The permission authorization enforcement is performed when requests are executed through one of the Feature Store (Python) servers:
 
 * The online feature server (REST)
 * The offline feature server (Apache Arrow Flight) uses the gRPC communication protocol to exchange data. This server wraps calls to existing offline store implementations and exposes interfaces as Arrow Flight endpoints.
 * The registry server (gRPC)
 
-NOTE: If you configure the feature store with a local provider (the default), there is no permission enforcement when accessing the Feature Store API.
+NOTE: If you configure your Feature Store with a local provider (the default), there is no permission enforcement when accessing the Feature Store API.

modules/creating-a-feature-store-instance-in-a-data-science-project.adoc

@@ -93,7 +93,7 @@ A _provider_ is a customizable interface that provides default Feature Store com
 $ feast --help
 ----
 
-. To view the files for the feature store project, enter the following command:
+. To view the files for the Feature Store project, enter the following command:
 +
 ----
 $ ls -la

modules/feature-store-workflow.adoc

@@ -21,7 +21,7 @@ Installs and configures Feature Store, as described in _Chapter 2. Configuring F
 
 * Prepares features, as described in _Chapter 3: Defining features_:
 .  Creates a feature definition file.
-.  Defines the data sources and other feature store objects.
+.  Defines the data sources and other Feature Store objects.
 .  Makes features available for real-time inference.
 
 * Prepares features for model training and real-time inference, as described in _Chapter 4. Retrieving features for model training_:

modules/overview-of-feature-store.adoc

@@ -44,7 +44,7 @@ Server:: A feature server that serves pre-computed features online. There are th
 * *The offline feature server* - An Apache Arrow Flight Server that uses the gRPC communication protocol to exchange data. This server wraps calls to existing offline store implementations and exposes interfaces as Arrow Flight endpoints.
 * *The registry server* - A server that uses the gRPC communication protocol to exchange data. You can communicate with the server using any programming language that can make gRPC requests.
 
-UI:: A web-based graphical user interface (UI) for viewing all the feature store objects and their relationships with each other.
+UI:: A web-based graphical user interface (UI) for viewing all the Feature Store objects and their relationships with each other.
 
 Feature Store provides the following software capabilities:
 

modules/retrieving-online-features-for-model-inference.adoc

@@ -13,7 +13,7 @@ A feature service is an object that represents a logical group of features from
 
 Typically, you create one feature service per model version, allowing for tracking of the features used by models. The features retrieved from the online store can belong to many feature views.
 
-*Note:* When you apply a feature service, an actual feature store server is not deployed.
+*Note:* When you apply a feature service, an actual Feature Store server is not deployed.
 
 .Prerequisites
 

modules/viewing-feature-store-objects-in-the-web-based-ui.adoc

@@ -1,7 +1,7 @@
 :_module-type: PROCEDURE
 
 [id="viewing-feature-store-objects-in-the-web-based-ui_{context}"]
-= Viewing feature store objects in the web-based UI
+= Viewing Feature Store objects in the web-based UI
 
 [role='_abstract']
 You can use the Feature Store Web UI to view all registered features, data sources, entities, and feature services.
@@ -42,7 +42,7 @@ The Feature Store Operator starts a container for the web-based Feature Store UI
 +
 You should see a deployment for the web-based UI. Note that OpenShift enables TLS by default at runtime.
 
-. To populate the web-based UI with the objects in your feature store:
+. To populate the web-based UI with the objects in your Feature Store instance:
 .. In the OpenShift console, select *Workloads* -> *Pods*. 
 .. Make sure that your project (for example, `my-ds-project`) is selected. 
 .. Click the `feast` pod and then select *Pod details*.