From 9750768d8b82ac3b7350fdd070eb1c1e0c33e2ad Mon Sep 17 00:00:00 2001
From: Kellen <9484709+goodroot@users.noreply.github.com>
Date: Wed, 22 Sep 2021 12:27:53 -0700
Subject: [PATCH] Fix the other one...

---
 dev_docs/key_concepts/persistable_state.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev_docs/key_concepts/persistable_state.mdx b/dev_docs/key_concepts/persistable_state.mdx
index 36ad6f128d6e0..4368417170eed 100644
--- a/dev_docs/key_concepts/persistable_state.mdx
+++ b/dev_docs/key_concepts/persistable_state.mdx
@@ -11,7 +11,7 @@ tags: ['kibana','dev', 'contributor', 'api docs']
  
 ## Exposing state that can be persisted
 
-Any plugin that exposes state that another plugin might persist should implement <DocLink id="kibKibanaUtilsPluginApi " section="def-common.PersistableStateService" text="`PersistableStateService`"/> interface on their `setup` contract. This will allow plugins persisting the state to easily access migrations and other utilities.
+Any plugin that exposes state that another plugin might persist should implement <DocLink id="kibKibanaUtilsPluginApi" section="def-common.PersistableStateService" text="`PersistableStateService`"/> interface on their `setup` contract. This will allow plugins persisting the state to easily access migrations and other utilities.
 
 Example: Data plugin allows you to generate filters. Those filters can be persisted by applications in their saved 
 objects or in the URL. In order to allow apps to migrate the filters in case the structure changes in the future, the Data plugin implements `PersistableStateService` on <DocLink id="kibDataQueryPluginApi" section="def-public.FilterManager" text="`data.query.filterManager`"/>.