fix images

llm-based-extractions/prompt-tips/list-tips.mdx

@@ -23,7 +23,7 @@ This method is an alternative to the [NLP Table](/llm-based-extractions/prompt-t
 
 The following example shows using the List method to extract data from a restaurant menu:
 
-![Click to enlarge](/images/list_instruct.png)
+![Click to enlarge](/assets/v0/images/screenshots/list_instruct.png)
 
 To try out this example in the Sensible app, take the following steps: 
 
@@ -42,7 +42,7 @@ To try out this example in the Sensible app, take the following steps:
 
 For example, use the following screenshot as a guide for configuring the `dinners` field:
 
-![Click to enlarge](/images/list_instruct_2.png)
+![Click to enlarge](/assets/v0/images/screenshots/list_instruct_2.png)
 
 ## Notes
 

llm-based-extractions/prompt-tips/query-group-tips.mdx

@@ -31,7 +31,7 @@ Combining queries for the location, phone number, and email into the same group
 
 The following example shows using the Query Group method to extract agricultural data from a government report:
 
-![Click to enlarge](/images/query_group_instruct.png)
+![Click to enlarge](/assets/v0/images/screenshots/query_group_instruct.png)
 
 To try out this example in the Sensible app, take the following steps: 
 
@@ -53,7 +53,7 @@ To try out this example in the Sensible app, take the following steps:
 | late fee amount                                               | String          |
 | fee in dollars for returned checks or rejected payments       | Currency        |
 
-![Click to enlarge](/images/query_group_instruct_1.png)
+![Click to enlarge](/assets/v0/images/screenshots/query_group_instruct_1.png)
 
 ## Notes
 

llm-based-extractions/prompt-tips/table-tips.mdx

@@ -17,7 +17,7 @@ This Sensible Instruct method extracts a table in a document based on your descr
 
 The following example shows using the NLP Table method to extract data from a bank statement:
 
-![Click to enlarge](/images/quickstart_instruct_4.png)
+![Click to enlarge](/assets/v0/images/screenshots/quickstart_instruct_4.png)
 
 To try out this example in the Sensible app, take the following steps: 
 
@@ -34,21 +34,21 @@ Click the **Send** icon for each column.
 
 3. To verify the extracted data, scroll down in the right pane and compare the **Extracted data** section to the document in the left pane:
 
-![Click to enlarge](/images/quickstart_instruct_5.png)
+![Click to enlarge](/assets/v0/images/screenshots/quickstart_instruct_5.png)
 
 4. (**Optional**) To standardize the representation of the extracted dates and dollar amounts, configure `date` and `currency` types as shown in the following screenshots:
 
-![Click to enlarge](/images/quickstart_instruct_6.png)
+![Click to enlarge](/assets/v0/images/screenshots/quickstart_instruct_6.png)
 
  You should see that the formatting of the extracted data changes according to the types you specified. For example, Sensible reformats the date `04/11/23` to a standardized output format, `2023-04-11`:
 
-![Click to enlarge](/images/quickstart_instruct_7.png)
+![Click to enlarge](/assets/v0/images/screenshots/quickstart_instruct_7.png)
 
 ### Example 2
 
 The following example shows using the NLP Table method to extract data from an auto insurance document:
 
-![Click to enlarge](/images/nlp_table_instruct.png)
+![Click to enlarge](/assets/v0/images/screenshots/nlp_table_instruct.png)
 
 To try out this example in the Sensible app, take the following steps: 
 
@@ -66,7 +66,7 @@ To try out this example in the Sensible app, take the following steps:
 
 For example, use the following screenshot as a guide for configuring the `insured_vehicles_table` field:
 
-![Click to enlarge](/images/nlp_table_instruct_2.png)
+![Click to enlarge](/assets/v0/images/screenshots/nlp_table_instruct_2.png)
 
 ## Notes
 

llm-based-extractions/prompt.mdx

@@ -12,7 +12,7 @@ When you write a prompt in a Sensible Instruct method, Sensible combines your pr
 
 See the following image for an example of a full prompt that Sensible inputs to an LLM for the [Query Group](/llm-based-extractions/prompt-tips/query-group-tips) method: 
 
-![Click to enlarge](/images/prompt.png)
+![Click to enlarge](/assets/v0/images/screenshots/prompt.png)
 
 The following table shows parameters that configure parts of the full prompt and that are global, or common to all Sensible Instruct methods:
 
@@ -25,11 +25,11 @@ The following table shows parameters that configure parts of the full prompt and
 
 You can configure all of these parameters in the SenseML editor and in the Sensible Instruct editor. For example, the following screenshots show prompt settings in Sensible Instruct for a Query Group field: 
 
-![Click to enlarge](/images/prompt_instruct_1.png)
+![Click to enlarge](/assets/v0/images/screenshots/prompt_instruct_1.png)
 
 The following screenshot shows prompt settings in Sensible Instruct for all fields in a config:
 
-![Click to enlarge](/images/prompt_instruct_2.png)
+![Click to enlarge](/assets/v0/images/screenshots/prompt_instruct_2.png)
 
 ## Global Sensible Instruct parameters
 

senseml-reference/advanced-computed-field-methods/add-computed-fields.mdx

@@ -23,11 +23,11 @@ The following example shows how to transform extracted tables so they're consist
 
 In the following example, Insurer A excludes the vehicle VIN and model from their policy limits table. In contrast, Insurer B includes the vehicle VIN, model, and make in their limits table:
 
-![Click to enlarge](/images/add_computed_fields_3.png)
+![Click to enlarge](/assets/v0/images/screenshots/add_computed_fields_3.png)
 
 This example uses the Add Computed Fields method to ensure that each table contains the same field IDs (`vin`, `policy_start`, `limits`, `amount`, and `model`):
 
-![Click to enlarge](/images/add_computed_fields_2.png)
+![Click to enlarge](/assets/v0/images/screenshots/add_computed_fields_2.png)
 
 To ensure consistency, this example transforms the tables as follows:
 
@@ -206,7 +206,7 @@ To ensure consistency, this example transforms the tables as follows:
 **Example document**  
 The following image shows the example document used with this example config:
 
-![Click to enlarge](/images/add_computed_fields_1.png)
+![Click to enlarge](/assets/v0/images/screenshots/add_computed_fields_1.png)
 
 | Example document | [Download link](https://raw.githubusercontent.com/sensible-hq/sensible-docs/main/readme-sync/assets/v0/pdfs/add%5Fcomputed%5Ffields.pdf) |
 | ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |

senseml-reference/advanced-computed-field-methods/custom-computation.mdx

@@ -273,7 +273,7 @@ The following example shows defining custom computed fields.
 **Example document**  
 The following image shows the example document used with this example config:
 
-![Click to enlarge](/images/add_computed_fields_1.png)
+![Click to enlarge](/assets/v0/images/screenshots/add_computed_fields_1.png)
 
 | Example document | [Download link](https://raw.githubusercontent.com/sensible-hq/sensible-docs/main/readme-sync/assets/v0/pdfs/add%5Fcomputed%5Ffields.pdf) |
 | ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
@@ -560,7 +560,7 @@ The following example shows using the Custom Computation method to perform the f
 **Example document**  
 The following image shows the example document used with this example config:
 
-![Click to enlarge](/images/blog_custom_computations.png) 
+![Click to enlarge](/assets/v0/images/screenshots/blog_custom_computations.png) 
 
 | Example document | [Download link](https://raw.githubusercontent.com/sensible-hq/sensible-docs/main/readme-sync/assets/v0/pdfs/blog%5Fcustom%5Fcomputations.pdf) |
 | ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |

senseml-reference/advanced-computed-field-methods/get-file-metadata.mdx

@@ -35,7 +35,7 @@ The following example shows extracting the filename from the example document.
 **Example document**  
 The following image shows the example document used with this example config:
 
-![Click to enlarge](/images/get_file_metadata.png)
+![Click to enlarge](/assets/v0/images/screenshots/get_file_metadata.png)
 
 | Example document | [Download link](https://raw.githubusercontent.com/sensible-hq/sensible-docs/main/readme-sync/assets/v0/pdfs/utility%5Fstatement%5Fgas%5Fdec%5F2019.pdf) |
 | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |

senseml-reference/computed-field-methods/concatenate.mdx

@@ -77,7 +77,7 @@ The following example shows using the Concat method to concatenate two address f
 
 The following image shows the example document used with this example config:
 
-![Click to enlarge](/images/concat.png)
+![Click to enlarge](/assets/v0/images/screenshots/concat.png)
 
 | Example document | [Download link](https://raw.githubusercontent.com/sensible-hq/sensible-docs/main/readme-sync/assets/v0/pdfs/concat.pdf) |
 | ---------------- | ----------------------------------------------------------------------------------------------------------------------- |

senseml-reference/computed-field-methods/constant.mdx

@@ -59,7 +59,7 @@ The following example shows adding a form name and policy duration as constants
 ```
 **Example document**
 
-![Click to enlarge](/images/constant.png)
+![Click to enlarge](/assets/v0/images/screenshots/constant.png)
 
 | Example document | [Download link](https://raw.githubusercontent.com/sensible-hq/sensible-docs/main/readme-sync/assets/v0/pdfs/auto%5Finsurance%5Fanyco.pdf) |
 | ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |

senseml-reference/computed-field-methods/mapper.mdx

@@ -58,7 +58,7 @@ The following example shows using a mapper to standardize a time duration.
 
 The following image shows the example document used with this example config:
 
-![Click to enlarge](/images/mapper.png)
+![Click to enlarge](/assets/v0/images/screenshots/mapper.png)
 
 | Example document | [Download link](https://raw.githubusercontent.com/sensible-hq/sensible-docs/main/readme-sync/assets/v0/pdfs/mapper.pdf) |
 | ---------------- | ----------------------------------------------------------------------------------------------------------------------- |

senseml-reference/computed-field-methods/pick-values.mdx

@@ -115,7 +115,7 @@ The following example shows returning a single value from a radio button group,
 
 The following image shows the example document used with this example config:
 
-![Click to enlarge](/images/pick_values.png)
+![Click to enlarge](/assets/v0/images/screenshots/pick_values.png)
 
 | Example document | [Download link](https://raw.githubusercontent.com/sensible-hq/sensible-docs/main/readme-sync/assets/v0/pdfs/pick%5Fvalues.pdf) |
 | ---------------- | ------------------------------------------------------------------------------------------------------------------------------ |

senseml-reference/computed-field-methods/split.mdx

@@ -59,7 +59,7 @@ The following example shows splitting a field's output to extract a first and la
 
 The following image shows the example document used with this example config:
 
-![Click to enlarge](/images/split.png)
+![Click to enlarge](/assets/v0/images/screenshots/split.png)
 
 | Example document | [Download link](https://raw.githubusercontent.com/sensible-hq/sensible-docs/main/readme-sync/assets/v0/pdfs/split.pdf) |
 | ---------------- | ---------------------------------------------------------------------------------------------------------------------- |

senseml-reference/computed-field-methods/suppress-output.mdx

@@ -55,7 +55,7 @@ The following example shows suppressing a raw "driver's name" field and outputti
 
 The following image shows the example document used with this example config:
 
-![Click to enlarge](/images/suppress_output.png)
+![Click to enlarge](/assets/v0/images/screenshots/suppress_output.png)
 
 | Example document | [Download link](https://raw.githubusercontent.com/sensible-hq/sensible-docs/main/readme-sync/assets/v0/pdfs/suppress%5Foutput.pdf) |
 | ---------------- | ---------------------------------------------------------------------------------------------------------------------------------- |

senseml-reference/computed-field-methods/zip.mdx

@@ -80,7 +80,7 @@ Notes:
 
 The following image shows the example document used with this example config:
 
-![Click to enlarge](/images/zip.png)
+![Click to enlarge](/assets/v0/images/screenshots/zip.png)
 
 | Example document | [Download link](https://raw.githubusercontent.com/sensible-hq/sensible-docs/main/readme-sync/assets/v0/pdfs/zip.pdf) |
 | ---------------- | -------------------------------------------------------------------------------------------------------------------- |
@@ -258,7 +258,7 @@ The following example shows using `"match":"allWithNull"` as an alternative to [
 **Example document**  
 The following image shows the example document used with this example config:
 
-![Click to enlarge](/images/all_with_null.png)
+![Click to enlarge](/assets/v0/images/screenshots/all_with_null.png)
 
 | Example document | [Download link](https://raw.githubusercontent.com/sensible-hq/sensible-docs/main/readme-sync/assets/v0/pdfs/all%5Fwith%5Fnull.pdf) |
 | ---------------- | ---------------------------------------------------------------------------------------------------------------------------------- |

senseml-reference/concepts/anchor-nuances.mdx

@@ -84,10 +84,10 @@ Here is an ending line.
 ```
 For **Anchor 1**, Sensible anchors on the last Match array element if it's preceded by the other array elements in order. `"match":all"` finds two anchors. See the following image for an illustration: 
 
-![Click to enlarge](/images/anchor_2.png)
+![Click to enlarge](/assets/v0/images/screenshots/anchor_2.png)
 
 * For **Anchor 2**, Sensible searches after the first instance of `here is an A line`, and discards anything earlier in the document. `"match":all"` finds four anchors. Notice it doesn't anchor on the first line B (`Here is a B line sneakily inserted before the intro line`) because that instance precedes the start match. See the following image for an illustration:  
-![Click to enlarge](/images/anchor_3.png)
+![Click to enlarge](/assets/v0/images/screenshots/anchor_3.png)
 
 Try out this example in the Sensible app using the following document and config:
 
@@ -201,7 +201,7 @@ The following example shows two anchors qualified by the Label method:
 
 The following image shows the example document used with this example config:
 
-![Click to enlarge](/images/ui_filtered_anchor.png)
+![Click to enlarge](/assets/v0/images/screenshots/ui_filtered_anchor.png)
 
 | Example document | [Download link](https://raw.githubusercontent.com/sensible-hq/sensible-docs/main/readme-sync/assets/v0/pdfs/row%5Fcolumn.pdf) |
 | ---------------- | ----------------------------------------------------------------------------------------------------------------------------- |

senseml-reference/concepts/coverage.mdx

@@ -23,7 +23,7 @@ Then its coverage is 75% : (18 - 1 - 2) / 20 = 0.75\.
 
 To view an individual extraction's coverage, click **Dashboard** and scroll to the **Recent** section:
 
-![Click to enlarge](/images/dashboard_coverage_1.png)
+![Click to enlarge](/assets/v0/images/screenshots/dashboard_coverage_1.png)
 
 In the preceding screenshot, get a coverage breakdown by viewing the extraction. You can view the extraction by clicking the extraction date in the **Recent extractions** column or downloading the Excel file.
 

senseml-reference/concepts/lines.mdx

@@ -4,7 +4,7 @@ title: "Lines"
 
 A _line_ is a rectangular region containing text. Sensible represents lines as gray boxes. Lines can occupy the same height on the page:
 
-![Click to enlarge](/images/line_concept.png)
+![Click to enlarge](/assets/v0/images/screenshots/line_concept.png)
 
  In other words, Sensible separates lines using any whitespace, not just newlines.
 
@@ -14,11 +14,11 @@ Sensible sorts lines primarily by their height on the page (their y-axis positio
 
 For example, this image shows which lines precede and succeed a target line:
 
-![Click to enlarge](/images/line_sort_1.png)
+![Click to enlarge](/assets/v0/images/screenshots/line_sort_1.png)
 
 When text such as handwriting is slightly misaligned vertically, line sorting is less intuitive. In the following image, a human reader may interpret the red line as succeeding the target line, but for Sensible it _precedes_ the target line because it's higher on the page:
 
-![Click to enlarge](/images/line_sort_2.png)
+![Click to enlarge](/assets/v0/images/screenshots/line_sort_2.png)
 
 To configure this default sorting behavior, see [the Sort Lines parameter](/senseml-reference/field-query-object/method).
 
@@ -28,6 +28,6 @@ To configure this default sorting behavior, see [the Sort Lines parameter](/sens
 
 For the Label method, Sensible groups lines together using whitespace and x- and y-axis positions. Sometimes, Sensible's line groups are more restrictive than a human reader might expect. In particular, Sensible groups lines separated by vertical space solely if they align at the _left_ edge of each line boundary by default:
 
-![Click to enlarge](/images/line_grouping.png)
+![Click to enlarge](/assets/v0/images/screenshots/line_grouping.png)
 
 To capture unaligned lines, use the [Document Range](/senseml-reference/methods/document-range) method.

senseml-reference/concepts/match-arrays.mdx

@@ -85,7 +85,7 @@ Use the Reverse parameter when a difficult-to-match target line precedes an easy
 
 The following image shows the example document used with this example config:
 
-![Click to enlarge](/images/reverse_1.png)
+![Click to enlarge](/assets/v0/images/screenshots/reverse_1.png)
 
 | Example document | [Download link](https://raw.githubusercontent.com/sensible-hq/sensible-docs/main/readme-sync/assets/v0/pdfs/reverse.pdf) |
 | ---------------- | ------------------------------------------------------------------------------------------------------------------------ |
@@ -104,4 +104,4 @@ The following image shows the example document used with this example config:
 
 In a reverse match array, Sensible searches for anchor candidates in sequence, and rules out overlapping match arrays. The following image illustrates this behavior for the example config:
 
-![Click to enlarge](/images/reverse_2.png)
+![Click to enlarge](/assets/v0/images/screenshots/reverse_2.png)

senseml-reference/concepts/section-nuances.mdx

@@ -8,7 +8,7 @@ The following images show the differing behaviors of sections and vertical secti
 
 ### Sections
 
-![Click to enlarge](/images/sections_concept_horizontal.png)
+![Click to enlarge](/assets/v0/images/screenshots/sections_concept_horizontal.png)
 
 Sensible finds the sections as follows:
 
@@ -24,7 +24,7 @@ Sensible finds the sections as follows:
 
 ### Vertical sections
 
-![Click to enlarge](/images/sections_concept_vertical.png)
+![Click to enlarge](/assets/v0/images/screenshots/sections_concept_vertical.png)
 
 Sensible:
 
@@ -68,7 +68,7 @@ For example, if you select the "Apple" and "Banana" columns by configuring `"col
 ```
 1. The Banana section contains the Banana, Nutrition, and Notes columns. For example, you can find the cell containing `105` in the Bananas column using the same `fruit_calories` field as in the preceding step. In other words, you _don't_ have to configure `"tiebreaker": "second"`.
 
-![Click to enlarge](/images/vertical_section_column_selection.png)
+![Click to enlarge](/assets/v0/images/screenshots/vertical_section_column_selection.png)
 
 As steps 2 and 3 in the previous image illustrate, the varying gap sizes between columns in each section mean that you can't use coordinate-based methods such as the Region method for fields in these sections.
 
@@ -91,6 +91,6 @@ For horizontal sections, you can create a section starting at each newline if yo
 
 In this case, Sensible creates sections by splitting text into "rows" at each newline. For more information about the behavior shown in the following image, see the [Zip sections example](/senseml-reference/sections/sections-example-zip).
 
-![Click to enlarge](/images/sections_match_all_anchors.png)
+![Click to enlarge](/assets/v0/images/screenshots/sections_match_all_anchors.png)
 
 For vertical sections, specifying the regular expression `".+"` for the Match parameter can be useful for repeating vertical sections that lack good anchor match candidates. In these situations, you must also nest the section group in a parent section group. For more information, see [Table grid example](/senseml-reference/sections/sections-example-table-grid).

senseml-reference/concepts/senseml.mdx

@@ -23,7 +23,7 @@ Here's a simple example of a field:
 ```
 The following image shows this example in the Sensible app:
 
-![Click to enlarge](/images/basic_field.png)
+![Click to enlarge](/assets/v0/images/screenshots/basic_field.png)
 
 As the preceding image shows, here's the output of the example field: