Outdated Sequence Diagram on Orchestration landing page

[amessbee]

There is a sequence diagram of an example flow on Orchestration landing page that seems outdated. In particular,

• OrchLib seems to have been renamed.
• provideOrchestartion is not use by the contract function explicitly rather is wrapped in a call to withOrchestration. Not sure if we want to keep it as is.
• Anything else?

Also, if there is a way to reduce the overall size of the diagram, and/or increase the font size, that should help with readability. Perhaps we can remove AgoricNames?

[amessbee]

@dckc
@turadg

Can you please have a look at the diagram and add/edit comments?