[RFC] Add reviewers' suggestions.

Author: Sventimir

rfcs/0050-genesis-ledger-export.md

@@ -19,8 +19,10 @@ node operators.
 ## Detailed design
 
 The genesis ledger export is achieved using a GraphQL field named
-`fork_config`. This field, if asked for, contains a new runtime
-configuration, automatically updated with:
+`fork_config`. Asking for this field requires providing a slot or a
+state hash of the block that we want to base the exported ledger on.
+This field, if asked for, contains a new runtime configuration,
+automatically updated with:
 
 * the dump of the current **staged ledger**, which will become the
 genesis ledger for the new network
@@ -43,7 +45,9 @@ migration script which will adapt a `mainnet` config file to the
 format required by `berkeley`. The former solution would probably
 be better.
 
-The `fork_config` field has been added to GraphQL in [PR #13787](https://github.com/MinaProtocol/mina/pull/13787).
+The `fork_config` field has been added to GraphQL in [PR #13787](https://github.com/MinaProtocol/mina/pull/13787). It needs to be extended to return the blockchain state for
+a given block (height or state hash) so that we can export the
+desired ledger after the blockchain has moved on.
 
 ## Drawbacks