Fix documentation inconsistency (#1510)

* Fix documentation inconsistency * Fix documentation spelling mistake
feast-dev · Apr 27, 2021 · c483145 · c483145
1 parent 2b2a4d3
commit c483145
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/docs/concepts/apply.md b/docs/concepts/apply.md
@@ -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.
 

diff --git a/docs/feast-on-kubernetes/concepts/entities.md b/docs/feast-on-kubernetes/concepts/entities.md
@@ -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