update doc

Author: gaurpulkit

docs/features.rst

@@ -42,6 +42,25 @@ You can also select specific list of models to run the health check on by provid
 
     datapilot dbt project-health --manifest-path ./target/manifest.json --select "path:dir1 path:dir2 model1 model2"
 
-This will run the health check on all the models in the 'dir1' and 'dir2' directory. It will also run the health check on the 'model1' and 'model2' models.
+This will run the health check on all the models in the 'dir1' and 'dir2' directory, as well as the 'model1' and 'model2' models.
 As of now, the '--select' flag only supports filtering based on model path and model name. We will add support for other filters and make it compatible
-with the dbt comands soon.
+with the dbt commands soon.
+
+3. **Configuration**:
+You can provide configuration in two ways:
+
+a. Using a local config file:
+    .. code-block:: shell
+
+        datapilot dbt project-health --manifest-path ./target/manifest.json --config-path ./path/to/config.yml
+
+b. Using a named config from the API:
+    .. code-block:: shell
+
+        datapilot dbt project-health --manifest-path ./target/manifest.json --config-name "my-config" --token "YOUR_API_TOKEN" --instance-name "YOUR_INSTANCE"
+
+The ``--config-name`` option allows you to use a configuration stored in the Altimate API. When using this option, you must also provide:
+- ``--token``: Your API token for authentication
+- ``--instance-name``: Your tenant ID
+
+If both ``--config-path`` and ``--config-name`` are provided, the local config file (``--config-path``) takes precedence.