Update docs/fault-proof-alpha/immunefi.md

Co-authored-by: protolambda <proto@protolambda.com>

docs/fault-proof-alpha/immunefi.md

@@ -30,7 +30,7 @@ The alpha system is not prepared for mainnet, and as such, there are a number of
     The remaining pre-images types are not supported, as the types are not used by the current op-program, but may be supported for future program proving, e.g. type 3 for application-specific proofs, and new types 4, 5, etc. for ethereum extensions like SHA2 and KZG point verification.
 1. Non-standard rollup chain configurations do not qualify. Output roots span a range of L2 blocks derived from a range of L1 blocks, built on top of the previous agreed upon L2 state. By breaking time or input-range chain parameters, the proof program may not complete or fail in undefined ways.
 ### Reviewer Notes
-1. **Any bug report without a PoC in the form of a test in `op-e2e` will not be considered a valid bug report.**
+1. **Any bug report without a proof-of-concept in the form of a test in `op-e2e` will not be considered a valid bug report.**
     1. A guide on creating an e2e test with an invalid output proposal to dispute can be found [here][invalid-proposal-doc].
 1. Exploits against the alpha system that take advantage of the aforementioned issues will not be considered valid bug reports.
 1. The [AlphabetVM][alphabet-vm] is not equivalent to the MIPS thread context in behavior. Bug reports submitted against the [AlphabetVM][alphabet-vm] will not be considered valid bug reports, this mock VM is used solely for testing.