This is one of the the first bits of template markup that we are probably not going to throw out once we get full prototype markup from the designers. As a result, we should consider replacing these literal English string with [internationalized versions](https://docs.djangoproject.com/en/dev/topics/i18n/translation/).

I would suggest modifying _benefits_for_trees in ecobenefits/views.py to include a translated label for each benefit. A Spanish tree map would return something like this:

```python
{
  ...
  "airquality": {
    value: 12
    unit: "kg"
    label: "Calidad del aire"
  }
  ...
}
```

This template can then be generalized to

```html
<tr><td>{{ benefits.airquality.label }}<td>{{ benefits.airquality.value }}</td></tr>
```

and then simplified further into a loop that iterates over the keys in ``benefits``