diff --git a/pgml-cms/blog/announcing-support-for-aws-us-east-1-region.md b/pgml-cms/blog/announcing-support-for-aws-us-east-1-region.md
index 2486bbcdc..e4b3e7a71 100644
--- a/pgml-cms/blog/announcing-support-for-aws-us-east-1-region.md
+++ b/pgml-cms/blog/announcing-support-for-aws-us-east-1-region.md
@@ -27,14 +27,8 @@ To demonstrate the impact of moving the data closer to your application, we've c
-\
-
-
-\
-
-
## Using the New Region
To take advantage of latency savings, you can [deploy a dedicated PostgresML database](https://postgresml.org/signup) in `us-east-1` today. We make it as simple as filling out a very short form and clicking "Create database".
diff --git a/pgml-cms/blog/generating-llm-embeddings-with-open-source-models-in-postgresml.md b/pgml-cms/blog/generating-llm-embeddings-with-open-source-models-in-postgresml.md
index f35e0081e..3ffa41d73 100644
--- a/pgml-cms/blog/generating-llm-embeddings-with-open-source-models-in-postgresml.md
+++ b/pgml-cms/blog/generating-llm-embeddings-with-open-source-models-in-postgresml.md
@@ -18,7 +18,7 @@ Montana Low
April 21, 2023
-PostgresML makes it easy to generate embeddings from text in your database using a large selection of state-of-the-art models with one simple call to **`pgml.embed`**`(model_name, text)`. Prove the results in this series to your own satisfaction, for free, by signing up for a GPU accelerated database.
+PostgresML makes it easy to generate embeddings from text in your database using a large selection of state-of-the-art models with one simple call to `pgml.embed(model_name, text)`. Prove the results in this series to your own satisfaction, for free, by signing up for a GPU accelerated database.
This article is the first in a multipart series that will show you how to build a post-modern semantic search and recommendation engine, including personalization, using open source models.
@@ -216,9 +216,6 @@ For comparison, it would cost about $299 to use OpenAI's cheapest embedding mode
| GPU | 17ms | $72 | 6 hours |
| OpenAI | 300ms | $299 | millennia |
-\
-
-
You can also find embedding models that outperform OpenAI's `text-embedding-ada-002` model across many different tests on the [leaderboard](https://huggingface.co/spaces/mteb/leaderboard). It's always best to do your own benchmarking with your data, models, and hardware to find the best fit for your use case.
> _HTTP requests to a different datacenter cost more time and money for lower reliability than co-located compute and storage._
diff --git a/pgml-cms/blog/meet-us-at-the-2024-postgres-conference.md b/pgml-cms/blog/meet-us-at-the-2024-postgres-conference.md
index d55070bd4..7ef738cfc 100644
--- a/pgml-cms/blog/meet-us-at-the-2024-postgres-conference.md
+++ b/pgml-cms/blog/meet-us-at-the-2024-postgres-conference.md
@@ -22,7 +22,6 @@ Why should you care? It's not every day you get to dive headfirst into the world
Save 25% on your ticket with our discount code: 2024\_POSTGRESML\_25
{% endhint %}
-\
PostgresML CEO and founder, Montana Low, will kick off the event on April 17th with a keynote about navigating the confluence of hardware evolution and machine learning technology.
We’ll also be hosting a masterclass in retrieval augmented generation (RAG) on April 18th. Our own Silas Marvin will give hands-on guidance to equip you with the ability to implement RAG directly within your database.
@@ -36,5 +35,3 @@ If you’d like some 1:1 time with our team at PgConf [contact us here](https://
So, why sit on the sidelines when you could be right in the thick of it, soaking up knowledge, making connections, and maybe even stumbling upon your next big breakthrough? Clear your schedule, grab your ticket, and get ready to geek out with us in San Jose.
See you there!
-
-\
diff --git a/pgml-cms/blog/mindsdb-vs-postgresml.md b/pgml-cms/blog/mindsdb-vs-postgresml.md
index 2b38b2c5a..e1349bc3c 100644
--- a/pgml-cms/blog/mindsdb-vs-postgresml.md
+++ b/pgml-cms/blog/mindsdb-vs-postgresml.md
@@ -47,9 +47,6 @@ Both Projects integrate several dozen machine learning algorithms, including the
| Full Text Search | - | ✅ |
| Geospatial Search | - | ✅ |
-\
-
-
Both MindsDB and PostgresML support many classical machine learning algorithms to do classification and regression. They are both able to load ~~the latest LLMs~~ some models from Hugging Face, supported by underlying implementations in libtorch. I had to cross that out after exploring all the caveats in the MindsDB implementations. PostgresML supports the models released immediately as long as underlying dependencies are met. MindsDB has to release an update to support any new models, and their current model support is extremely limited. New algorithms, tasks, and models are constantly released, so it's worth checking the documentation for the latest list.
Another difference is that PostgresML also supports embedding models, and closely integrates them with vector search inside the database, which is well beyond the scope of MindsDB, since it's not a database at all. PostgresML has direct access to all the functionality provided by other Postgres extensions, like vector indexes from [pgvector](https://github.com/pgvector/pgvector) to perform efficient KNN & ANN vector recall, or [PostGIS](http://postgis.net/) for geospatial information as well as built in full text search. Multiple algorithms and extensions can be combined in compound queries to build state-of-the-art systems, like search and recommendations or fraud detection that generate an end to end result with a single query, something that might take a dozen different machine learning models and microservices in a more traditional architecture.
@@ -300,9 +297,6 @@ PostgresML is the clear winner in terms of performance. It seems to me that it c
| translation\_en\_to\_es | t5-base | 1573 | 1148 | 294 |
| summarization | sshleifer/distilbart-cnn-12-6 | 4289 | 3450 | 479 |
-\
-
-
There is a general trend, the larger and slower the model is, the more work is spent inside libtorch, the less the performance of the rest matters, but for interactive models and use cases there is a significant difference. We've tried to cover the most generous use case we could between these two. If we were to compare XGBoost or other classical algorithms, that can have sub millisecond prediction times in PostgresML, the 20ms Python service overhead of MindsDB just to parse the incoming query would be hundreds of times slower.
## Clouds
diff --git a/pgml-cms/docs/api/apis.md b/pgml-cms/docs/api/apis.md
index 15f1dd37f..6ce0afec6 100644
--- a/pgml-cms/docs/api/apis.md
+++ b/pgml-cms/docs/api/apis.md
@@ -11,7 +11,7 @@ We also provide Client SDKs that implement the best practices on top of the SQL
## SQL Extension
PostgreSQL is designed to be _**extensible**_. This has created a rich open-source ecosystem of additional functionality built around the core project. Some [extensions](https://www.postgresql.org/docs/current/contrib.html) are include in the base Postgres distribution, but others are also available via the [PostgreSQL Extension Network](https://pgxn.org/).\
-\
+
There are 2 foundational extensions included in a PostgresML deployment that provide functionality inside the database through SQL APIs.
* **pgml** - provides Machine Learning and Artificial Intelligence APIs with access to more than 50 ML algorithms to train classification, clustering and regression models on your own data, or you can perform dozens of tasks with thousands of models downloaded from HuggingFace.
diff --git a/pgml-cms/docs/resources/benchmarks/mindsdb-vs-postgresml.md b/pgml-cms/docs/resources/benchmarks/mindsdb-vs-postgresml.md
index 581c846b8..02c8824c0 100644
--- a/pgml-cms/docs/resources/benchmarks/mindsdb-vs-postgresml.md
+++ b/pgml-cms/docs/resources/benchmarks/mindsdb-vs-postgresml.md
@@ -35,7 +35,6 @@ Both Projects integrate several dozen machine learning algorithms, including the
| Full Text Search | - | ✅ |
| Geospatial Search | - | ✅ |
-\
Both MindsDB and PostgresML support many classical machine learning algorithms to do classification and regression. They are both able to load ~~the latest LLMs~~ some models from Hugging Face, supported by underlying implementations in libtorch. I had to cross that out after exploring all the caveats in the MindsDB implementations. PostgresML supports the models released immediately as long as underlying dependencies are met. MindsDB has to release an update to support any new models, and their current model support is extremely limited. New algorithms, tasks, and models are constantly released, so it's worth checking the documentation for the latest list.
Another difference is that PostgresML also supports embedding models, and closely integrates them with vector search inside the database, which is well beyond the scope of MindsDB, since it's not a database at all. PostgresML has direct access to all the functionality provided by other Postgres extensions, like vector indexes from [pgvector](https://github.com/pgvector/pgvector) to perform efficient KNN & ANN vector recall, or [PostGIS](http://postgis.net/) for geospatial information as well as built in full text search. Multiple algorithms and extensions can be combined in compound queries to build state-of-the-art systems, like search and recommendations or fraud detection that generate an end to end result with a single query, something that might take a dozen different machine learning models and microservices in a more traditional architecture.
Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.