From f1427d7ca8e158a59f49a226ab97e12613487488 Mon Sep 17 00:00:00 2001 From: Stian Thorgersen Date: Fri, 17 Mar 2017 09:28:08 +0100 Subject: [PATCH] Fix garbage collections to garbage collected --- server_development/topics/user-storage/provider-interfaces.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/server_development/topics/user-storage/provider-interfaces.adoc b/server_development/topics/user-storage/provider-interfaces.adoc index 54527d1d7e..8bf3b6778f 100644 --- a/server_development/topics/user-storage/provider-interfaces.adoc +++ b/server_development/topics/user-storage/provider-interfaces.adoc @@ -55,7 +55,7 @@ You may be thinking that the `UserStorageProvider` interface is pretty sparse? there are other mix-in interfaces your provider class may implement to support the meat of user integration. `UserStorageProvider` instances are created once per transaction. When the transaction is complete, the -`UserStorageProvider.close()` method is invoked and the instance is then garbage collections. Instances are created +`UserStorageProvider.close()` method is invoked and the instance is then garbage collected. Instances are created by provider factories. Provider factories implement the `org.keycloak.storage.UserStorageProviderFactory` interface. [source,java]