Update EIP-7685: two typos in eip-7685.md

Merged by EIP-Bot.

EIPS/eip-7685.md

@@ -89,7 +89,7 @@ EL request.
 
 ### Opaque byte array rather than an RLP array
 
-By having the second byte on be opaque bytes, rather than an RLP (or other
+By having the bytes of `request_data` array from second byte on be opaque bytes, rather than an RLP (or other
 encoding) list, we can support different encoding formats for the transaction
 payload in the future such as SSZ, LEB128, or a fixed width format.
 
@@ -110,7 +110,7 @@ The authors' recommendations on source and validity of requests are:
   converted into a request.
 * A request's validity can often not be fully verified at the execution layer.
   This is why they are referred to merely as "requests"; they do not carry the
-  authority on their own unilaterally catalyze and action. We expect the system
+  authority on their own to unilaterally catalyze an action. We expect the system
   contracts to perform whatever validation is possible by the EL and then pass
   it on to the CL for further validation.