Resolving publication conflicts for PR#605

site/about/overview-llm-features.qmd

@@ -5,7 +5,6 @@ date: last-modified
 
 {{< var vm.product >}} offers several specialized features that use large language models (LLMs) to streamline model risk management and ensure regulatory compliance. Here's how we approach these features and what you need to know. 
 
-
 ::: {.attn}
 ## {{< fa list-check >}} Our philosophy
 
@@ -16,8 +15,7 @@ date: last-modified
 
 :::
 
-::: {.w-80-ns}
-
+::: {.w-75-ns}
 At {{< var vm.product >}}, our approach to AI features, particularly in testing and risk management, reflects a philosophy of _drinking our own champagne_ or using our own products. This means that while we create risk management tools for our users, we also rigorously apply these tools and practices within our own product development.
 
 Our testing methodologies and philosophy around testing are readily available, and we openly share information about our approach. Specific test results are also available on request, allowing us to demonstrate the same standards of robustness and compliance that we promote for our users.

site/releases/2023/2023-aug-15/highlights.qmd

@@ -17,7 +17,7 @@ This release includes a number of improvements for the developer experience when
 
 We made a number of enhancements to the {{< var validmind.developer >}} to improve the experience for developers.
 
-**Better test organization**
+##### Better test organization
 
 :::: {.flex .flex-wrap .justify-around}
 
@@ -32,7 +32,7 @@ Added a `metadata` and `tags` attribute to the `Test` base class for better cate
 
 ::::
 
-**Better filtering**
+##### Better filtering
 
 :::: {.flex .flex-wrap .justify-around}
 
@@ -49,7 +49,7 @@ Added a new `task_type` argument to the `list_tests()` function to allow simple
 ::::
 
 
-**Clearer naming**
+##### Clearer naming
 
 Renamed `required_context` to `required_inputs` across the whole {{< var vm.product >}} {{< var validmind.api >}}.
 
@@ -58,7 +58,7 @@ Renamed `required_context` to `required_inputs` across the whole {{< var vm.prod
 
 To make the discovery of required context and default configuration easier, this update includes a number of changes to how `required_context` and `default_parameters` are presented.
 
-**Preview template expansion**
+##### Preview template expansion
 
 :::: {.flex .flex-wrap .justify-around}
 
@@ -74,7 +74,7 @@ With `vm.preview_template()`, you can now view detailed, expandable information
 
 ::::
 
-**Simplified test listing**
+##### Simplified test listing
 
 :::: {.flex .flex-wrap .justify-around}
 
@@ -90,7 +90,7 @@ The `vm.tests.list_tests()` function has been refined to show only the `ID`, `Na
 
 ::::
 
-**Detailed test descriptions**
+##### Detailed test descriptions
 
 :::: {.flex .flex-wrap .justify-around}
 
@@ -106,7 +106,7 @@ You can now obtain complete test details, including `required_context` and `defa
 
 ::::
 
-**Retrieve test suite**
+##### Retrieve test suite
 
 :::: {.flex .flex-wrap .justify-around}
 
@@ -122,7 +122,7 @@ The new function `vm.get_test_suite()` allows you to access a specific test suit
 
 ::::
 
-**Access to default configuration**
+##### Access to default configuration
 
 :::: {.flex .flex-wrap .justify-around}
 
@@ -138,7 +138,7 @@ A new method, `get_default_config()`, is now part of both the TestPlan and TestS
 
 ::::
 
-**Easier required context**
+##### Easier required context
 
 :::: {.flex .flex-wrap .justify-around}