Update origins.md

Author: dsyme

origins.md

@@ -8,7 +8,7 @@ SpecLang is conceptualized as a compiler for natural language: specs are _perman
 
 Another core concept of Copilot Workspace is the all-important “Co” in "Copilot" — the core idea that the human and the AI take a journey together — a continual _pas de deux_ where the human indicates an intention and the AI makes an offering and the human checks and corrects that offering, or ignores it, and the cycle continues. This is a core challenge in task-oriented workflows. Among all the talk of “agents”, this need to design for this repeated AI-human divergence and alignment can be lost. If the AI is going to take steps towards a solution, it must “take the human with it”, and allow review, steering and control at every step of the way. Put differently, if agents are to be human-assistive, they must be “co-agents”. This requires close attention to user experience, and also requires top-rate user experience developers. We don't say we've fully cracked it — but the design principle has been there with us from the start.
 
-From June 2023 to GitHub Universe in November 2023 and through to technical preview in April 2024, the EEA ideation merged with many practical themes and become Copilot Workspace. We began to focus on [GitHub issues](https://github.com/features/issues) and tasks as the source of change intent. We looked at validation and the possibilities to incorporate AI-assisted build and validation cycles. We did user studies and learned more about the many ways we could support iteration after initial code generation. We looked at extensibility and [“developer flow” integration into GitHub.com](https://github.com/githubnext/copilot-workspace-user-manual/blob/main/overview.md#task). We experimented with AI inference for working out what files — and what parts of files — to change. We integrated a [terminal](https://github.com/githubnext/copilot-workspace-user-manual/blob/main/overview.md#integrated-terminal) and file synchronizer for practical validation. We redesigned in [Primer](https://github.com/primer) to align with GitHub. We started to learn about [the joy of natural language programming on mobile devices](https://www.youtube.com/watch?v=Zv6TuVzcRdY) — drafting issues on-the-go, then “Open in Workspace” and save the results for later. We iterated on [conceptual models of the development process](https://github.blog/2024-01-17-a-developers-second-brain-reducing-complexity-through-partnership-with-ai/), doing interviews with developers to help understand how they experience and use Chat-based AI in their work today, and what scenarios they welcome yet more AI assistance with. We talked widely and openly about the project in GitHub and Microsoft, and were plain, open and honest about our methodology and status, and started to work with partner teams. We began to understand more of the social role of AI-assisted tooling including sharing “sessions” — early drafts of possible code changes. We also learned how Copilot Workspace helps as much when the developer is unfamiliar with a codebase as familiar. We dug through logs to identify faulty GPU clusters or 502s. We worked hard, very hard, on the user experience. And we used the tool ourselves — so-called “dogfooding” — a lot, every day.
+From June 2023 to GitHub Universe in November 2023 and through to technical preview in April 2024, the EEA ideation merged with many practical themes to become Copilot Workspace. We began to focus on [GitHub issues](https://github.com/features/issues) and tasks as the source of change intent. We looked at validation and the possibilities to incorporate AI-assisted build and validation cycles. We did user studies and learned more about the many ways we could support iteration after initial code generation. We looked at extensibility and [“developer flow” integration into GitHub.com](https://github.com/githubnext/copilot-workspace-user-manual/blob/main/overview.md#task). We experimented with AI inference for working out what files — and what parts of files — to change. We integrated a [terminal](https://github.com/githubnext/copilot-workspace-user-manual/blob/main/overview.md#integrated-terminal) and file synchronizer for practical validation. We redesigned in [Primer](https://github.com/primer) to align with GitHub. We started to learn about [the joy of natural language programming on mobile devices](https://www.youtube.com/watch?v=Zv6TuVzcRdY) — drafting issues on-the-go, then “Open in Workspace” and save the results for later. We iterated on [conceptual models of the development process](https://github.blog/2024-01-17-a-developers-second-brain-reducing-complexity-through-partnership-with-ai/), doing interviews with developers to help understand how they experience and use Chat-based AI in their work today, and what scenarios they welcome yet more AI assistance with. We talked widely and openly about the project in GitHub and Microsoft, and were plain, open and honest about our methodology and status, and started to work with partner teams. We began to understand more of the social role of AI-assisted tooling including sharing “sessions” — early drafts of possible code changes. We also learned how Copilot Workspace helps as much when the developer is unfamiliar with a codebase as familiar. We dug through logs to identify faulty GPU clusters or 502s. We worked hard, very hard, on the user experience. And we used the tool ourselves — so-called “dogfooding” — a lot, every day.
 
 We're excited to continue this development and to take the journey through technical preview, always with the aim to learn more, every single day.