Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix documentation inconsistency #1510

Merged
merged 2 commits into from
Apr 27, 2021
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/concepts/apply.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ Feast will scan Python files in your feature repository, and find all Feast obje

If all definitions look valid, Feast will sync the metadata about Feast objects to the registry. The registry is a tiny database storing most of the same information you have in the feature repository. This step is necessary because the production feature serving infrastructure won't be able to access Python files in the feature repository at run time, but it will be able to efficiently and securely read the feature definitions from the registry.

### 3. Create cloud infrastructure
#### 3. Create cloud infrastructure

Feast CLI will create all necessary infrastructure for feature serving and materialization to work. What exactly gets created depends on which provider is configured to be used in `feature_store.yaml` in the feature repository.

Expand Down
2 changes: 1 addition & 1 deletion docs/feast-on-kubernetes/concepts/entities.md
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@ Permitted changes include:

* The entity's description and labels

The following changes are note permitted:
The following changes are not permitted:

* Project
* Name of an entity
Expand Down