Merge branch 'main' of github.com:box/developer.box.com into staging

Author: anastasiaberyoza

content/guides/webhooks/triggers.md

@@ -64,7 +64,7 @@ available for folders.
 | `SIGN_REQUEST.DECLINED` | A sign request is declined. | Yes | Yes |
 | `SIGN_REQUEST.EXPIRED` | A sign request is expired. | Yes | Yes |
 | `SIGN_REQUEST.SIGNER_EMAIL_BOUNCED` | A signer's email is bounced. | Yes | Yes |
-| `SIGN_REQUEST.SIGNER_SIGNED` | A sign request is signed. | Yes | Yes |
+| `SIGN_REQUEST.SIGNER_SIGNED` | A sign request is signed by a particular signer. | Yes | Yes |
 | `SIGN_REQUEST.SIGNATURE_REQUESTED` | A signature is requested from a signer. | Yes | Yes |
 | `SIGN_REQUEST.ERROR_FINALIZING` | An error occurred while finalizing a sign request. | Yes | Yes |
 | `WEBHOOK.DELETED` | A webhook is deleted. | No | No |

content/pages/sign/40-webhooks/index.md

@@ -17,7 +17,7 @@ This is particularly important since the signature requests are asynchronous,
 and the signers can interact with them at any time, possibly outside of your 
 application.
 
-## Sign related events
+## Sign-related events
 
 There are Box Sign-related events that can trigger the webhooks. Like most of Box events the listeners are set at the folder or document level.
 
@@ -31,6 +31,6 @@ Some examples of events that can be listened to are:
 - `SIGN_REQUEST.DECLINED`, when a signature request is declined.
 - `SIGN_REQUEST.EXPIRED`, when a signature request expires.
 - `SIGN_REQUEST.SIGNER_EMAIL_BOUNCED`, when a signer's email is bounced.
-- `SIGN_REQUEST.SIGNER_SIGNED`, when the signature request is signed.
+- `SIGN_REQUEST.SIGNER_SIGNED`, when the signature request is signed by a particular signer.
 - `SIGN_REQUEST.SIGNATURE_REQUESTED`, when the signature is requested from the signer.
 - `SIGN_REQUEST.ERROR_FINALIZING`, when the signature request could not be processed.