Merge pull request #8567 from ethereum-optimism/jg/fix_lint

Fix line length lint

specs/span-batches.md

@@ -160,9 +160,9 @@ equal to `MAX_RLP_BYTES_PER_CHANNEL`). Therefore every field size of span batch
 `MAX_SPAN_BATCH_SIZE` . There can be at least single span batch per channel, and channel size is limited
 to `MAX_RLP_BYTES_PER_CHANNEL` and you may think that there is already an implicit limit. However, having an explicit
 limit for span batch is helpful for several reasons. We may save computation costs by avoiding malicious input while
-decoding. For example, let's say bad batcher wrote span batch which `block_count = max.Uint64`. We may early return using
-the explicit limit, not trying to consume data until EOF is reached. We can also safely preallocate memory for decoding
-because we know the upper limit of memory usage.
+decoding. For example, let's say bad batcher wrote span batch which `block_count = max.Uint64`. We may early return
+using the explicit limit, not trying to consume data until EOF is reached. We can also safely preallocate memory for
+decoding because we know the upper limit of memory usage.
 
 ## Span batch Activation Rule