Fixing paths in documentation

docs/reference/ingredients/LLMJoin.md

@@ -25,11 +25,11 @@ BlendSQL was built to interact with tables "in-the-wild", and many (such as thos
 For this reason, we can leverage the internal knowledge of a pre-trained LLM to do the `JOIN` operation for us.
 
 ### `JoinProgram`
-::: blendsql.ingredients.builtin.llm.join.main.JoinProgram
+::: blendsql.ingredients.builtin.join.main.JoinProgram
     handler: python
     show_source: true
 
 ### `LLMJoin`
-::: blendsql.ingredients.builtin.llm.join.main.LLMJoin
+::: blendsql.ingredients.builtin.join.main.LLMJoin
     handler: python
     show_source: true

docs/reference/ingredients/LLMMap.md

@@ -25,11 +25,11 @@ SELECT merchant FROM transactions
 The temporary table shown above is then combined with the original "transactions" table with an `INNER JOIN` on the "merchant" column.
 
 ### `MapProgram`
-::: blendsql.ingredients.builtin.llm.map.main.MapProgram
+::: blendsql.ingredients.builtin.map.main.MapProgram
     handler: python
     show_source: true
 
 ### `LLMMap`
-::: blendsql.ingredients.builtin.llm.map.main.LLMMap
+::: blendsql.ingredients.builtin.map.main.LLMMap
     handler: python
     show_source: true

docs/reference/ingredients/LLMQA.md

@@ -125,11 +125,11 @@ Or, from our running example:
 The above BlendSQL will yield the result `AIG`, since it appears in the `Symbol` column from `account_history`.
 
 ### `QAProgram`
-::: blendsql.ingredients.builtin.llm.qa.main.QAProgram
+::: blendsql.ingredients.builtin.qa.main.QAProgram
     handler: python
     show_source: true
 
 ### `LLMQA`
-::: blendsql.ingredients.builtin.llm.qa.main.LLMQA
+::: blendsql.ingredients.builtin.qa.main.LLMQA
     handler: python
     show_source: true