linting

mckinsey · Mar 26, 2024 · 1a8b05a · 1a8b05a
1 parent d3e6963
commit 1a8b05a
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/vizro-core/docs/pages/development/documentation-style-guide.md b/vizro-core/docs/pages/development/documentation-style-guide.md
@@ -155,4 +155,4 @@ Functional is not try-hard, cliched or hyperbolic:
 * **Colloquialisms**. Avoid them "like the plague" because they may not translate to other regions/languages.
 * **Technical terminology**. This applies particularly to acronyms that do not pass the "Google test". If it is not possible to find their meaning from a simple Google search, don't use them, or explain them with a link or some text.
 * **Business speak**. You can explain simply without using words like "leverage", "utilize" or "facilitate" and still sound clever.
-<!-- vale on -->
+<!-- vale on -->
diff --git a/vizro-core/docs/pages/explanation/why-vizro.md b/vizro-core/docs/pages/explanation/why-vizro.md
@@ -125,4 +125,4 @@ There are a number of cases where alternatives to Vizro may be more suitable, in
 - where development teams already contain designers and JavaScript (or equivalent) engineers with bandwidth to build bespoke applications (though Vizro can sometimes still be used effectively to rapidly prototype potential solutions)
 
 - where Python developers are already very comfortable leveraging other Python packages
-<!-- vale on -->
+<!-- vale on -->