P2P clarifications when introducing engine_getBlobsV1

specs/deneb/p2p-interface.md

@@ -312,11 +312,11 @@ Clients SHOULD NOT respond with sidecars related to blocks that fail the beacon
 
 ###### Usage of `engine_getBlobsV1` engine API method
 In addition to `BlobSidecarsByRoot` requests, recent blobs recovery MAY also be done by querying the Execution Layer via `engine_getBlobsV1`.
-Implementers are encouraged to leverege this method to encrease the likelyhood of incorporating and attesting to the last block when its proposer is not able to publish blobs on time.
+Implementers are encouraged to leverege this method to encrease the likelihood of incorporating and attesting to the last block when its proposer is not able to publish blobs on time.
 
 Client MAY use this method when serving `BlobSidecarsByRoot` requests.
 
-Client MUST publish the corresponding `blob_sidecar` whenever succesfully recovers blobs via `engine_getBlobsV1`.
+Client MUST publish the corresponding `blob_sidecar` whenever successfully recovers blobs via `engine_getBlobsV1`.
 
 ##### BlobSidecarsByRange v1