From 02e8de6e75e900699422fe3549fb6d3ed13965aa Mon Sep 17 00:00:00 2001
From: "Scott E. Graves" <scott.e.graves@protonmail.com>
Date: Sun, 23 Feb 2025 19:23:48 -0600
Subject: [PATCH] Update Providers

---
 Providers.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/Providers.md b/Providers.md
index 8befdca..895fa4d 100644
--- a/Providers.md
+++ b/Providers.md
@@ -2,7 +2,7 @@
 
 `repertory` currently supports 3 different back-end providers: `S3`, `Sia` and `Encryption`.
 
-### S3
+### S3 Provider
 
 * The S3 provider utilizes the de facto standard AWS S3 HTTP REST API via `libcurl`.
 * An access key and secret key are required for operation, configured via `S3Config.AccessKey` and `S3Config.SecretKey` in `config.json`
@@ -12,11 +12,11 @@
    * Locally, files remain unencrypted. The encryption/decryption process takes place while transferring to/from the S3 provider.
    * This is enabled by specifying a secure password via the `S3Config.EncryptionToken` setting in `config.json`. 
 
-### Sia
+### Sia Provider
 
 * The Sia provider utilizes the `renterd` native HTTP REST API via `libcurl`
 
-### Encryption
+### Encryption Provider
 
 #### [WIP-Use with caution]