lint

specs/networking/p2p-interface.md

@@ -178,7 +178,7 @@ Additional topics are used to propagate lower frequency validator messages. Thei
 
 #### Interop
 
-Unaggregated and aggregated attestations from all shards are sent as `Attestation` to the `beacon_aggregate_and_proof` topic. Clients are not required to publish aggregate attestations but must be able to process them. All validating clients SHOULD try to perform local attestation aggregation to prepare for block proposing.
+Unaggregated and aggregated attestations from all shards are sent as `Attestation`s to the `beacon_aggregate_and_proof` topic. Clients are not required to publish aggregate attestations but must be able to process them. All validating clients SHOULD try to perform local attestation aggregation to prepare for block proposing.
 
 #### Mainnet
 

specs/validator/0_beacon-chain-validator.md

@@ -359,7 +359,7 @@ Some validators are selected to locally aggregate attestations with a similar `a
 
 ### Aggregation selection
 
-A validator is selected to aggregate based upon the following
+A validator is selected to aggregate based upon the return value of `is_aggregator()`.
 
 ```python
 def slot_signature(state: BeaconState, slot: Slot, privkey: int) -> BLSSignature:
@@ -399,10 +399,9 @@ Let `aggregate_attestation.aggregation_bits` be a `Bitlist[MAX_VALIDATORS_PER_CO
 Set `aggregate_attestation.signature = aggregate_signature` where `aggregate_signature` is obtained from:
 
 ```python
-def get_aggregate_signature(attestations: Attestation) -> BLSSignature:
+def get_aggregate_signature(attestations: Sequence[Attestation]) -> BLSSignature:
     signatures = [attestation.signature for attestation in attestations]
-    aggregate_signature = bls_aggregate_signatures(signatures)
-    return aggregate_signature
+    return bls_aggregate_signatures(signatures)
 ```
 
 ### Broadcast aggregate