New Magento 2 installs using test/dev/staging

Internal use only, but some info can be reworded for sellers.

This wording is in a Magento 2 customer facing FAQ (it has been reworded)

• You can install the Omnivore extension to your test/staging version of Magento and create an Omnivore account - always add 'TEST to the end of your retailer name so that we know its a test site.
• Installing to your test/staging Magento site is just to check that there is no negative impact on your Magento site. E.g load on your magento servers. Omnivore connects via the APIs so we are not adding any custom code to your magento site. Creating marketplace listings, marketplace set up etc is generally done in production. Some marketplaces have accounts for testing, but not all.
• When you connect to Omnivore, you will always connect to the production version of Omnivore

Other notes written by Deb

• Extra information that would be good either in a public FAQ or if not suitable an internal FAQ
• What needs to be done if a retailer wants to change the API Endpoint from their Magento staging site to their production site rather than setting up a brand-new Omnivore (we will need Will's input for this)
• When do we use the Alternate API Endpoint?
• If a retailer does install a new Omnivore, link to FAQ on how you can copy any category mappings etc to the new Omnivore account.
• Order testing options with a test/staging Magento/Omnivore (raise a ticket?)

I need to look into this:

Maybe a separate faq re Custom order create status in Magento  and Custom order complete status in Magento (rarely used but I cannot see any FAQ re this option)