fix(content): delete listings section (#1149)

filecoin-project · Sep 10, 2020 · 4d74206 · 4d74206
1 parent 1e0403d
commit 4d74206
Show file tree

Hide file tree

Showing 9 changed files with 2 additions and 123 deletions.
diff --git a/content/listings/_index.md b/content/listings/_index.md
diff --git a/content/listings/actors.md b/content/listings/actors.md
diff --git a/content/listings/libp2p_protocols/_index.md b/content/listings/libp2p_protocols/_index.md
diff --git a/content/listings/libp2p_protocols/data_transfer_protocol.md b/content/listings/libp2p_protocols/data_transfer_protocol.md
diff --git a/content/listings/reserved_ranges.md b/content/listings/reserved_ranges.md
diff --git a/content/listings/system_map.md b/content/listings/system_map.md
diff --git a/content/systems/filecoin_blockchain/storage_power_consensus/_index.md b/content/systems/filecoin_blockchain/storage_power_consensus/_index.md
@@ -224,8 +224,6 @@ ValidateBeaconEntries(blockHeader, priorBlockHeader) error {
 
 Filecoin block headers also contain a single "ticket" generated from its epoch's beacon entry. Tickets are used to break ties in the Fork Choice Rule, for forks of equal weight.
 
-You can find the Ticket data structure [here](data_structures)
-
 Whenever comparing tickets in Filecoin, the comparison is that of the ticket's VRFDigest's bytes.
 
 ### Randomness Ticket generation

diff --git a/content/systems/filecoin_files/data_transfer/_index.md b/content/systems/filecoin_files/data_transfer/_index.md
@@ -81,7 +81,7 @@ once the provider indicates their intent to accept and publish the client's deal
 
 ## Protocol
 
-A data transfer CAN be negotiated over the network via the [Data Transfer Protocol](data_transfer_protocol), a libp2p protocol type.
+A data transfer CAN be negotiated over the network via the Data Transfer Protocol, a libp2p protocol type.
 
 Using the Data Transfer Protocol as an independent libp2p communciation mechanism is not a hard requirement -- as long as both parties have an implementation of the Data Transfer Subsystem that can talk to the other, any
 transport mechanism (including offline mechanisms) is acceptable.

diff --git a/content/systems/filecoin_vm/interpreter/vm_interpreter_old.md b/content/systems/filecoin_vm/interpreter/vm_interpreter_old.md
@@ -28,7 +28,7 @@ This second route for creating an actor is allowed to avoid the necessity of an
 
 ## Execution (Calling a method on an Actor)
 
-Message execution currently relies entirely on 'built-in' code, with a common external interface. The method and actor to call it on are specified in the `Method` and `To` fields of a message, respectively. Method parameters are encoded and put into the `Params` field of a message. The encoding is technically actor dependent, but for all built-in Filecoin actors it is the dag-cbor ipld encoding of the parameters struct for each method defined in [the actors doc](actors.md).
+Message execution currently relies entirely on 'built-in' code, with a common external interface. The method and actor to call it on are specified in the `Method` and `To` fields of a message, respectively. Method parameters are encoded and put into the `Params` field of a message. The encoding is technically actor dependent, but for all built-in Filecoin actors it is the dag-cbor ipld encoding of the parameters struct for each method defined in actors.
 
 ### Storage