fixup! documentation

Signed-off-by: Angelo De Caro <[email protected]>

Author: adecaro

docs/core-token.md

@@ -1,6 +1,6 @@
 # Example core.yaml section
 
-The following example provides descriptions for the various keys required for a Fabric Smart Client node that uses the Token SDK.
+The following example provides descriptions for the various keys required by the Token SDK.
 
 ```yaml
 # ------------------- Token SDK Configuration -------------------------
@@ -107,35 +107,4 @@ token:
                 SW:
                   Hash: SHA2
                   Security: 256
-  # Internal database to keep track of token transactions. 
-  # It is used by auditors and token owners to track history
-  ttxdb:
-    persistence:
-      # type can be one of badger, sql or memory.
-      type: badger
-      opts:
-        # persistence location
-        path: /some/path
-
-    # The sql driver uses golangs database/sql package internally.
-    # In theory you can use any driver if you import it in your application;
-    # for instance `import _ "github.com/mattn/go-sqlite3"` for the cgo version of sqlite.
-    # See https://github.com/golang/go/wiki/SQLDrivers. We only tested with github.com/lib/pq
-    # and modernc.org/sqlite, and it's likely that other drivers don't work exactly the same.
-    # To try a new sql driver, add a test here: token/services/ttxdb/db/sql/sql_test.go.
-    # 
-    # type: sql
-    # opts:
-    #   createSchema: true # create tables programmatically
-    #   tablePrefix: tsdk  # optional
-    #   driver: sqlite     # in the application, `import _ "modernc.org/sqlite"`
-    #   dataSource: /some/path/ttxdb.sqlite
-    #   maxOpenConns: 10  # by default this is 0 (unlimited), sets the maximum number of open connections to the database
-    #
-    # Alternative (`import _ "github.com/lib/pq"`).
-    # The 'dataSource' field can be sensitive (contain a password). In that case,
-    # set it in the TTXDB_DATASOURCE environment variable instead of in this file.
-    #   driver: postgres
-    #   dataSource: host=localhost port=5432 user=postgres password=example dbname=tokendb sslmode=disable
-
 ```

docs/services/identity.md

@@ -89,6 +89,6 @@ Both requires the identities to be stored on the filesystem following the Hyperl
 
 High level, these are the steps to follow:
 1. Instantiate the roles your driver will support.
-2. Instantiate the Wallet Registries for each role.
+2. Instantiate the Wallet Registry for each role.
 
-Let see an example taken from the [`fabtoken`](./../../token/core/fabtoken/driver) driver.
+See an example taken from the [`fabtoken`](./../../token/core/fabtoken/driver) driver.

docs/services/vault.md

@@ -23,9 +23,9 @@ The Token Vault service empowers you with a comprehensive suite of functionaliti
         * **ListHistoryIssuedTokens()**: This function delivers a detailed list of all tokens that have been issued within the network.
     * **Public Parameters:** The PublicParams() function retrieves the public parameters associated with the token system.
     * **Token Information Retrieval:** These functions provide mechanisms to access information about your tokens:
-        * **GetTokenInfos(ids []*token.ID, callback QueryCallbackFunc)**: This function retrieves information for the provided token IDs. It employs a callback function (`QueryCallbackFunc`) to unmarshal the retrieved token information for efficient processing.
-        * **GetTokenOutputs(ids []*token.ID, callback QueryCallbackFunc)**: Similar to the previous function, this function retrieves the raw token outputs stored on the ledger for the provided IDs. It utilizes a callback function (`QueryCallbackFunc`) for unmarshalling the retrieved data.
-        * **GetTokenInfoAndOutputs(ids []*token.ID, callback QueryCallback2Func)**: This function offers a combined approach, retrieving both the token information and their corresponding outputs for the provided IDs. It employs a dedicated callback function (`QueryCallback2Func`) tailored for handling both data types.
+        * **GetTokenInfos(ids []*token.ID)**: This function retrieves information for the provided token IDs.
+        * **GetTokenOutputs(ids []*token.ID)**: Similar to the previous function, this function retrieves the raw token outputs stored on the ledger for the provided IDs.
+        * **GetTokenInfoAndOutputs(ids []*token.ID)**: This function offers a combined approach, retrieving both the token information and their corresponding outputs for the provided IDs.
     * **GetTokens:** This function retrieves a list of tokens along with their corresponding vault keys.
     * **WhoDeletedTokens:** This function delves into the history of deleted tokens. It provides information about who deleted the specified tokens (if applicable) and returns a boolean array indicating whether each token at a given position has been deleted.