fix: update dbt example code to fix typo (#1772)

content/en/hosting/analytics/building-dbt-models.md

@@ -186,7 +186,7 @@ This example extracts `Last Menstrual Period`, `Expected Delivery Date` and `ANC
 -- add any indexes specific to this form
 {%- set form_indexes = [
   {'columns': ['edd']},
-  {'columns': ['danger_signs']}]
+  {'columns': ['danger_signs']},
   {'columns': ['risk_factors']}]
 -%}
 -- add columns specific to this form

content/en/hosting/analytics/setup-docker-compose.md

@@ -24,7 +24,7 @@ This guide will walk you through setting up a deployment of CHT Sync with the CH
 
 In the `cht-sync` folder, copy the values from the `env.template` file to a `.env` file. For more information, see the references on the [Environment variables page]({{< relref "hosting/analytics/environment-variables" >}}).
 
-For production CHT Core deployments, the port will most likely need to be set to `443` like this: `COUCHDB_PORT=443`. This is because CHT Core uses an `nginx` [reverse proxy]({{< relref "core/overview/architecture#overview" >}}) on port `443`, instead of the default `5984` port used in a stand-alone CouchDB instance which the `env.template` [has]({{< relref "hosting/analytics/environment-variables" >}}).
+Configure the `COUCHDB_*` environment variables to connect to your CouchDB instance. For production CHT Core deployments, the port will most likely need to be set to `443` like this: `COUCHDB_PORT=443`. This is because CHT Core uses an `nginx` [reverse proxy]({{< relref "core/overview/architecture#overview" >}}) on port `443`, instead of the default `5984` port used in a stand-alone CouchDB instance which the `env.template` [has]({{< relref "hosting/analytics/environment-variables" >}}).
 
 {{% alert title="Note" %}}
 The first time you run the commands from any of the sections below it will need to download many Docker images and will take a while. You'll know it's done when you see `#8 DONE 0.0s` and you are returned to the command line. Be patient!