anchor.diff:          emojis: 🤡
   ```
   
  -This example will install [buildkite-plugins/detect-clowns-buildkite-plugin](https://github.com/buildkite-plugins/detect-clowns-buildkite-plugin) when your pipeline is evaluated and run it for 
  +This example will install the (hypothetical) `buildkite-plugins/detect-clowns-buildkite-plugin` 
  +when your pipeline is evaluated and run it for 
   this build step.
   
  -A real-life example is the [docker-compose](https://github.com/buildkite-plugins/docker-compose-buildkite-plugin) plugin. It provides an integration with docker-compose that assists with running 
  -your builds within a docker environment:
  +A real-life example is the [docker-compose plugin]. It provides an integration 
  +with docker-compose that assists with running your builds within a docker environment:
   
   ```yml
   steps:
  
positive.code:         workdir: /app
  ```
  
  And then the logic of the (simplified) [command hook] script in `hooks/command`:
  
  ```bash
  #!/bin/bash
  
negative.code: 
  The agent parses the plugin block and passes the parameters through to the script as environment variables in the form `BUILDKITE_PLUGIN_{NAME}_{KEY}`, or if a list is provided then `BUILDKITE_PLUGIN_{NAME}_{KEY}_{IDX}`. 
  
  This lets a script supplement the [standard environment variables] that the agent provides to any script with structured configuration from the plugin definition. 
  
  Plugins are also able to offer `command` and `environment` hooks, which aren't allowed in per-project hooks. This lets plugins change how commands are executed entirely.
  
  