odh-23178-3 feature store - peer review (#894)

Author: MelissaFlinn

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

@@ -3,18 +3,18 @@
 ifdef::context[:parent-context: {context}]
 
 [id="customizing-your-feature-store-configuration_{context}"]
-= Customizing your feature store configuration
+= Customizing your Feature Store configuration
 
 [role='_abstract']
-Optionally, you can apply the following configurations to your feature store instance:
+Optionally, you can apply the following configurations to your Feature Store instance:
 
 * Configure an offline store
 * Configure an online store
 * Configure the feature registry
 * Configure persistent volume claims (PVCs)
 * Configure role-based access control (RBAC)
 
-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_.
+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 
 link:https://github.com/feast-dev/feast/blob/stable/infra/feast-operator/docs/api/markdown/ref.md[Feast API documentation^].

modules/configuring-an-offline-store.adoc

@@ -4,7 +4,7 @@
 = Configuring an offline store
 
 [role='_abstract']
-When you create a feature store instance that uses the minimal configuration, by default, Feature Store uses a SQLite file-based store for the offline store.
+When you create a Feature Store instance that uses the minimal configuration, by default, Feature Store uses a SQLite file-based store for the offline store.
 
 The example in the following procedure shows how to configure DuckDB for the offline store.
 

modules/configuring-an-online-store.adoc

@@ -4,7 +4,7 @@
 = Configuring an online store
 
 [role='_abstract']
-When you create a feature store instance using the minimal configuration, by default, the online store is a SQLite database.
+When you create a Feature Store instance using the minimal configuration, by default, the online store is a SQLite database.
 
 The example in the following procedure shows how to configure a PostgreSQL database for the online store.
 

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

@@ -1,7 +1,7 @@
 :_module-type: PROCEDURE
 
 [id="creating-a-feature-store-instance-in-a-data-science-project_{context}"]
-= Creating a feature store instance in a data science project
+= Creating a Feature Store instance in a data science project
 
 [role='_abstract']
 You can add an instance of Feature Store to a data science project by creating a custom resource definition (CRD) in the OpenShift console.
@@ -65,7 +65,7 @@ spec:
 +
 The `spec.feastProjectDir` references a Feature Store project that is in the Git repository for a Credit Store tutorial.
 
-. Optionally, change the `metadata.name` for the feature store instance.
+. Optionally, change the `metadata.name` for the Feature Store instance.
 . Optionally, edit `feastProject`, which is the namespace for organizing your Feature Store instance. Note that this project is not the {productname-short} data science project.
 
 . Click *Create*.
@@ -154,10 +154,10 @@ The `feature_store.yaml` file defines the following components:
 
 * *entity_key_serialization_version* - Specifies the serialization scheme that Feature Store uses when writing data to the online store. 
 
-*NOTE:* Although the `offline_store` location is not included in the `feature_store.yaml` file, the feature store instance uses a DASK file-based offline store. In the `feature_store.yaml` file, the registry type is `file` but it uses a simple SQLite database.
+*NOTE:* Although the `offline_store` location is not included in the `feature_store.yaml` file, the Feature Store instance uses a DASK file-based offline store. In the `feature_store.yaml` file, the registry type is `file` but it uses a simple SQLite database.
 
 .Next steps
 
-* Optionally, you can customize the default configurations for the offline store, online store, or registry by editing the YAML configuration for the Feature Store CR, as described in _Customizing your feature store configuration_.
+* Optionally, you can customize the default configurations for the offline store, online store, or registry by editing the YAML configuration for the Feature Store CR, as described in _Customizing your Feature Store configuration_.
 
 * Give your ML engineers and data scientists access to the data science project so that they can create a workbench. and provide them with a copy of the `feature_store.yaml` file so that they can add it to their workbench IDE, such as Jupyter.

modules/editing-an-existing-feature-store-instance.adoc

@@ -1,16 +1,16 @@
 :_module-type: PROCEDURE
 
 [id="editing-an-existing-feature-store-instance_{context}"]
-= Editing an existing feature store instance
+= Editing an existing Feature Store instance
 
 [role='_abstract']
-The examples in this document describe how to customize a feature store instance by creating a new custom resource definition (CRD). Alternatively, you can customize an existing feature instance.
+The examples in this document describe how to customize a Feature Store instance by creating a new custom resource definition (CRD). Alternatively, you can customize an existing feature instance.
 
 .Prerequisites
 
 * You have cluster administrator privileges for your {openshift-platform} cluster.
 
-* You have created a feature store instance, as described in _Deploying a feature store instance in a data science project_.
+* You have created a Feature Store instance, as described in _Deploying a Feature Store instance in a data science project_.
 
 .Procedure
 
@@ -23,4 +23,4 @@ The examples in this document describe how to customize a feature store instance
 
 .Verification
 
-The feature store instance CRD deploys successfully.
+The Feature Store instance CRD deploys successfully.

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

@@ -63,7 +63,7 @@ features=feature_service,
 
 .Verification
 
-When you run the `feast` commands, you should see output similar to the following"
+When you run the `feast` commands, you should see output similar to the following:
 
 .Example output
 ----

modules/specifying-files-to-ignore.adoc

@@ -5,7 +5,7 @@
 
 When you run the `feast apply` command, Feature Store reads all Python files recursively, including Python files in subdirectories, even if the Python files do not contain feature definitions.
 
-If you have Python files, such as imperative scripts,  in your registry folder that you want Feature Store to ignore when you run the  feast apply command, you should create a `.feastignore` file and add a list of paths to all files that you want Feature Store to ignore.
+If you have Python files, such as imperative scripts, in your registry folder that you want Feature Store to ignore when you run the feast apply command, you should create a `.feastignore` file and add a list of paths to all files that you want Feature Store to ignore.
 
 .Example .feastignore file
 ----

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

@@ -13,7 +13,7 @@ You can use the Feature Store Web UI to view all registered features, data sourc
 
 * You have enabled the Feature Store component, as described in _Enabling the Feature Store component_.
 
-* You have created a Feature Store CRD, as described in _Creating a feature store instance in a data science project_.
+* You have created a Feature Store CRD, as described in _Creating a Feature Store instance in a data science project_.
 
 .Procedure