fixup! fixup! fixup! fixup! fixup! [doc] Improvements on management of trusted certificates

Signed-off-by: Ming Lu <[email protected]>

Author: minglumlu

doc/content/design/trusted-certificates.md

@@ -73,30 +73,37 @@ This is an existing API to install a trusted certificate into the pool with its
 Prior to this design, the API's name parameter represents the certificate file name as persisted on the dom0 file system.
 In this design, this API will be deprecated because it exposes implementation details that should remain internal and hidden from users.
 The new "pool.install_trusted_certificate" should be used instead.
+For the same reason, "pool.uninstall_ca_certificate" will also be deprecated.
 
 ### pool.install_trusted_certificate
 This is a new API introduced in this design with its arguments being defined as:
 * session (ref session_id): reference to a valid session;
 * self (ref Pool): reference to the pool;
-* kind (string): the kind of the certificate; it can be either "ca" or "peer";
+* ca (boolean): the trusted certificate is a root CA certificate used to verify a chain (true), or a peer certificate used for certificate pinning (false);
 * cert (string): the trusted certificate in PEM format;
 * purpose (string list): the purposes of the trusted certificate.
 
 This new API is used to install trusted certificate.
-The value of *kind* can be "ca", which stands for root CA certificate, or "peer" which stands for peer certificate.
 When *purpose* is an empty set, it stands for a root CA certificate for general purpose.
-The *purpose* can not be an empty set when the *kind* is "peer", because each peer certificate is specific to a single server and therefore unsuitable for a shared trusted certificate for general purpose.
+The *purpose* can not be an empty set when the *ca* is false, because each peer certificate is specific to a single server and therefore unsuitable for a shared trusted certificate for general purpose.
+
+It returns *void* when succeed. Otherwise, return corresponding API error.
 
 ### pool.uninstall_certificate
 This is a new API introduced in this design to uninstall a trusted certificate with its arguments being defined as:
 * session (ref session_id): reference to a valid session;
 * certificate (ref Certificate): reference to the trusted certificate;
 * force (bool): remove the database entry even if the file doesn't exist.
 
+It returns *void* when succeed. Otherwise, return corresponding API error.
+
 ### pool.join
 Prior to this design, trusted certificates are exchanged between the pool and the joining host during the pre‑join phase.
 This design preserves that behavior to ensure the joiner works correctly both before and after joining the pool.
 
+### pool.eject
+The trusted certificates will be removed from any host which is being eject from the pool.
+
 ### Other APIs of managing trusted certificates
 The install/uninstall APIs above are not the only ways of managing the trusted certificates.
 A particular API, e.g. "pool.set_wlb_url", may also install the trusted certificate used to validate the WLB server on subsequent TLS connections.