Put in GDS style, removed marmite metaphor.

Define 'acceptance criteria'. This is the first (of many) mentions of acceptance criteria in the agile docs. An explanation here is essential.

"user story card" needs explaining - link it to the 'writing user stories' document

Can we delete this para? "To stop your meetings from becoming repetitive, have an object that you (gently) throw to someone to signify they should speak next. Pick people at random - it keeps people on their toes and lets the person speaking to choose the person they wish to hear from next. At GDS we use cuddly toys or a piece of fruit. It’s a bit of fun. You don’t have to this - it’s just something to experiment with." If it's something a few GDS teams do rather than agile methodology it's a bit cutesy for this document.

The marmite metaphor doesn't work - although the properties of Marmite might be good for you, they aren't exclusive to Marmite and can be provided by other products. Using an advertising slogan, now so old it's passed into cliche, is a big change in tone - from the authoritative to the avuncular - for this document.
completed one sentence erroneously cut in previous edit.
Put in GDS style

3 to 6 months, not 3-6 months; who's not who is. Is there an email address we can hyperlink this instruction 'please contact the assisted digital team at GDS'?
Truncations, bullet points, acronym markdown

Lots of 30+ word sentences broken up. Acronyms explained and put in markdown. 'Try and' changed to 'try to' several times.
Acronyms spelt out and put in markdown, the web/website/internet put in lower case.
Link to load balance, removed bold text and word 'deliver'
style guide compatibility 

Removed 'in order to', clarified points with plain English.
Very long sentences broken into 2 sentences or bullet pointed.
Put in GDS style

Changed & to and; facilitate to help; spelt out SLA, VPN and API and put acronyms in markdown
Acronyms, titles, markdown and grammar improved.

changed first header from question to title, likewise What are native apps; removed possessive apostrophe from "Digital Leaders meeting" as it's an attributive noun; API spelt out and put in markdown; removed 'so-called' modifier from 'apps'; linked to HTML5 explanation; removed PM's dashboard as it had no link unlike the other 3 examples; changed 3rd party to third party for consistency with other documents; full stops after each point in the numbered list.
Many changes to meet GDS style

contractions, four to 4, changed question that was answered to a statement, restructured sentence so it didn't start with the hanging participle 'depending on the needs of your particular project'; optimization to optimisation; long sentence bulleted; removed 'in order'; corrected spelling of accommodate
put in contractions
style guide compatibility 

S not z in spellings, broke up long paras, changed banned words, contractions used, bullet points start with lower case, as does government, full stops at end of numbered points, changed 'exploits' to 'failure'.
Full stops after numbered points; changed 'deliver', changed question header to title
Style and grammar corrected

removed bold text, bullet pointed long para, took out 'in order', changed tautological 'ELMS license application system' to Electronic License Management System
style guide compatibility 

Changed banned word 'robust', broke up 53-word sentence, put internet in lower case.
Changed 'why we do this' to a lead-in sentence as it's followed by bullet points.
Style changes: 2 important points still to be addressed

First bullet point needed a lead-in sentence. 

Removed the continuous integration link as there's nothing about C.I. there: /service-manual/agile/continuous-delivery.html
Crowdsourced as one word for consistency
All words in headers after the first word put in lower case
Load and performance testing not Load & performance testing

Still to do: define acceptance criteria. They're 1st mentioned in Features of agile, so explain the term there and link to it here. 
'Everyone is responsible for quality' this duplicates information in Quality. It only needs to be in 1 place and linked to from the other. https://www.gov.uk/service-manual/agile/quality.html - please decide where it should be.
Changed FAQ H3s, clarified points; more clarification required.

Clarified first sentence. 

"A transaction completed only partially online means the user may complete a single process within the overall transaction, like booking an appointment or completing a part of an application." What does this mean in terms of measurement? Will it be measured, or does it fall outside of the end to end process? Please clarify.
Full stop after numbered point; lead-in sentence to bullet point list.