Mintlify Docs Edits

[mintlify]

No description provided.

[Bijan-Massoumi]

I don't think we need the API Request Response column on the Statuses table.

[Bijan-Massoumi]

Likewise, I don't think we need the API Request Response column on this table.

[Bijan-Massoumi]

X-Posting here

The error section isn't quite right. The UNKNOWN , NATIVE CUSTOM error types describe how an EVM smart contract reverted during on-chain execution ( or pre-flight simulation). They are never used to describe Turnkey-defined or application-specific errors
Native — Built-in Solidity reverts: require(), assert(), plain revert()
Custom — Contract-defined errors using Solidity's error keyword
Unknown — Revert data we couldn't decode (missing ABI, unverified contract)

Turnkey application Errors such as signing, or policy rejection will be described in Error.Message and aren't classified by any specific error type

[MarkoKey]

Capturing this comment from @t-vila so I dont forget:

in the tx automation example https://turnkey-0e7c1f5b-sponsored-tx-docs-121.mintlify.app/signing-automation/code-examples/sending-sponsored-transactions@turnkey/core would not work on node.js servers, for backend people need to use @turnkey/sdk-serverI think we should be a little bit more explicit and have a 3rd point in SDK Overview3. Using server-side @turnkey/sdk-serverand I guess also mentioning how the sdk-server client is defined in Step 1import { Turnkey } from "@turnkey/sdk-server";

const client = new Turnkey({
apiBaseUrl: "https://api.turnkey.com/",
apiPrivateKey: process.env.TURNKEY_API_PRIVATE_KEY,
apiPublicKey: process.env.TURNKEY_API_PUBLIC_KEY,
defaultOrganizationId: process.env.TURNKEY_ORGANIZATION_ID,
}).apiClient();

[DeRauk]

While you're here, could you remove the (Coming soon) piece for mainnet?