message: rename in README in replay-tool(#3084)
diff: @@ -16,8 +16,8 @@ Replay-tool replays ops from op files generated by [fluid-fetch tool](../fluid-f
  ## Snapshot
  The snapshots will just appear in the --outdir in current directory. Filenames for snapshot will be like Snapshot_last_op_50.json and so on.
  - The snapshot service will take snapshot for the individual components in the container and then the snapshot of the whole state will be taken.
  - The snapshot for container will appear in --outdir/container and the snapshot for component will appear in --outdir/componentName/.
  + The snapshot service will take snapshot for the individual data store in the container and then the snapshot of the whole state will be taken.
  + The snapshot for container will appear in --outdir/container and the snapshot for data store will appear in --outdir/dataStoreName/.
  ## Investigating snapshot bugs
  @@ -35,4 +35,4 @@ The first file is result of snapshotting document.
  The second file is result of initializing new container with such snapshot (i.e. loading from snapshot) and generating another snapshot from that container (disabling optimizations around reusing existing content in storage),
  without processing any ops.
  The two files should be exactly the same! If they differ, that very likely points to a bug (and diff will point you where the bug is)!
  -Occasionally we may need to change runtime to write out snapshots in predictable way (i.e. sort order matters to do efficient diffs, like order of components in snapshot, or order of blobs - these things do not matter to runtime, but matter a lot when doing diffing of two snapshots).
  +Occasionally we may need to change runtime to write out snapshots in predictable way (i.e. sort order matters to do efficient diffs, like order of data stores in snapshot, or order of blobs - these things do not matter to runtime, but matter a lot when doing diffing of two snapshots).
  