add some code marks

Author: briwylde08

docs/build/guides/auth/contract-authorization.mdx

@@ -335,7 +335,7 @@ By using `env.current_contract_address()`, we can get the invoker's address and
 
 Custom account contracts are contracts that implement a special reserved function for validating externally provided signatures within the respective authorization context. The custom account contracts are essentially regular contracts, with an added capability to verify externally provided authorization.
 
-### \_\_check_auth()
+### `\_\_check_auth()`
 
 A contract that implements the `CustomAccountInterface` for authorizing calls becomes a custom account contract. The interface contains a single function called `__check_auth()`. The function is a reserved function, and it is invoked automatically by the Host when a contract authorizes a transaction. It cannot be called manually.
 
@@ -434,7 +434,7 @@ The test script creates a signer and a random payload. The contract function `in
 
 As this test case shows, `testing __check_auth()` is very simple using `try_invoke_contract_check_auth`, and it’s the recommended method of testing authorization `with __check_auth()`. See the simple account example for the full test code.
 
-#### set_auths()
+#### `set_auths()`
 
 :::Note