commit 3bebf1ea9278098f65c1ab9ef7d70a57c064600e
Author: David Moreau Simard <moi@dmsimard.com>
Date:   Thu Oct 15 12:47:15 2020 -0400

    docs: s/ara-api/ara-report/ for distributed sqlite
    
    At some point the default was changed from ara-api to ara-report and so
    it makes sense to use ara-report in the examples instead of ara-api.
    
    Change-Id: I9962565c8466e9afad01b80e2922af1f154a5f8b

diff --git a/doc/source/distributed-sqlite-backend.rst b/doc/source/distributed-sqlite-backend.rst
index 706f295..c632f0d 100644
--- a/doc/source/distributed-sqlite-backend.rst
+++ b/doc/source/distributed-sqlite-backend.rst
@@ -48,32 +48,32 @@ this::
 
     /var/www/logs/
     ├── 1
-    │   ├── ara-api
+    │   ├── ara-report
     │   │   └── ansible.sqlite
     │   └── console.txt
     ├── 2
     │   ├── logs.tar.gz
     │   └── some
     │       └── path
-    │           └── ara-api
+    │           └── ara-report
     │               └── ansible.sqlite
     └── 3
         ├── builds.txt
         ├── dev
-        │   └── ara-api
+        │   └── ara-report
         │       └── ansible.sqlite
         └── prod
-            └── ara-api
+            └── ara-report
                 └── ansible.sqlite
 
 With the above example file tree, a single instance of the API server with the
 distributed sqlite backend enabled would be able to respond to queries at the
 following endpoints:
 
-- http://example.org/1/ara-api
-- http://example.org/2/some/path/ara-api
-- http://example.org/3/dev/ara-api
-- http://example.org/3/prod/ara-api
+- http://example.org/1/ara-report
+- http://example.org/2/some/path/ara-report
+- http://example.org/3/dev/ara-report
+- http://example.org/3/prod/ara-report
 
 Configuration
 -------------