Rebuild docs

doc/protocol.md

@@ -159,7 +159,7 @@ The following table lists all of Maelstrom's defined errors.
 | 10 | not-supported | ✓ | Use this error to indicate that a requested operation is not supported by the current implementation. Helpful for stubbing out APIs during development. |
 | 11 | temporarily-unavailable | ✓ | Indicates that the operation definitely cannot be performed at this time--perhaps because the server is in a read-only state, has not yet been initialized, believes its peers to be down, and so on. Do *not* use this error for indeterminate cases, when the operation may actually have taken place. |
 | 12 | malformed-request | ✓ | The client's request did not conform to the server's expectations, and could not possibly have been processed. |
-| 13 | crash |   | Indicates that some kind of general, indefinite error occurred. Use this as a catch-all for errors you can't otherwise categorize, or as a starting point for your error handler: it's safe to return `internal-error` for every problem by default, then add special cases for more specific errors later. |
+| 13 | crash |   | Indicates that some kind of general, indefinite error occurred. Use this as a catch-all for errors you can't otherwise categorize, or as a starting point for your error handler: it's safe to return `crash` for every problem by default, then add special cases for more specific errors later. |
 | 14 | abort | ✓ | Indicates that some kind of general, definite error occurred. Use this as a catch-all for errors you can't otherwise categorize, when you specifically know that the requested operation has not taken place. For instance, you might encounter an indefinite failure during the prepare phase of a transaction: since you haven't started the commit process yet, the transaction can't have taken place. It's therefore safe to return a definite `abort` to the client. |
 | 20 | key-does-not-exist | ✓ | The client requested an operation on a key which does not exist (assuming the operation should not automatically create missing keys). |
 | 21 | key-already-exists | ✓ | The client requested the creation of a key which already exists, and the server will not overwrite it. |