Rethink 'Federated Digital Twins' BIS doc page

[ColinKerr]

The following issues were raised with the Federated Digital Twins doc page:

Page https://www.itwinjs.org/bis/guide/intro/federated-digital-twins - "Federated Digital Twins for Infrastructure Engineering"

• "Bentley defines "iTwin" as an Infrastructure Digital Twin, implemented as a federation of digital representations such as iModels, Reality Data, Sensor (IoT) Data, etc." "Federation"-> "group".
• "A Digital Twin should be a cohesive digital replica against which to write services and apps." "Replica" -> "copy"
• "usually because they were conceived before that was practical". "Conceived" -> "created", "developed"
• ", but because they are indecipherable without the original application program.". "Indecipherable" -> "can't be read"
• "Digital Twins facilitate operating existing built infrastructure". "Facilitate operating" -> "make easier to operate"

After review the page has larger problems than the ones raised. The whole page needs a rethink, what is its purpose and goal? It is one of the first pages in the BIS docs so it should have a strong purpose. The current document is out of date and lacks a well defined purpose.