fixed docs and added ollama as a first-class LLM provider

docs/source/concepts/tech_overview/listener.rst

@@ -22,7 +22,7 @@ Upstream (Egress)
 Arch automatically configures a listener to route requests from your application to upstream LLM API providers (or hosts).
 When you start Arch, it creates a listener for egress traffic based on the presence of the ``listener`` configuration
 section in the configuration file. Arch binds itself to a local address such as ``127.0.0.1:12000/v1`` or a DNS-based
-address like ``arch.local:12000/v1`` for outgoing traffic. For more details on LLM providers, read :ref:`here <llm_provider>`.
+address like ``arch.local:12000/v1`` for outgoing traffic. For more details on LLM providers, read :ref:`here <llm_providers>`.
 
 Configure Listener
 ^^^^^^^^^^^^^^^^^^

docs/source/concepts/tech_overview/terminology.rst

@@ -31,7 +31,7 @@ code to LLMs.
 
    When you start Arch, you specify a listener address/port that you want to bind downstream. But, Arch uses are predefined port
    that you can use (``127.0.0.1:12000``) to proxy egress calls originating from your application to LLMs (API-based or hosted).
-   For more details, check out :ref:`LLM provider <llm_provider>`.
+   For more details, check out :ref:`LLM providers <llm_providers>`.
 
 **Prompt Target**: Arch offers a primitive called :ref:`prompt target <prompt_target>` to help separate business logic from
 undifferentiated work in building generative AI apps. Prompt targets are endpoints that receive prompts that are processed by Arch.