update to Storage Connector Guides

Author: bubriks

docs/user_guides/fs/storage_connector/index.md

@@ -7,6 +7,7 @@ There are three main use cases for Storage Connectors:
 - Simply use it to read data from the storage into a dataframe.
 - [External (on-demand) Feature Groups](../../../concepts/fs/feature_group/external_fg.md) can be defined with storage connectors as data source. This way, Hopsworks stores only the metadata about the features, but does not keep a copy of the data itself. This is also called the Connector API.
 - Write [training data](../../../concepts/fs/feature_view/offline_api.md) to an external storage system to make it accessible by third parties.
+- Manage [feature group](../../../user_guides/fs/feature_group/create.md) that stores offline data in an external storage system.
 
 Storage connectors provide two main mechanisms for authentication: using credentials or an authentication role (IAM Role on AWS or Managed Identity on Azure). Hopsworks supports both a single IAM role (AWS) or Managed Identity (Azure) for the whole Hopsworks cluster or multiple IAM roles (AWS) or Managed Identities (Azure) that can only be assumed by users with a specific role in a specific project.