From edc80d48bdb4fa7e318beee3ab40d85201649291 Mon Sep 17 00:00:00 2001 From: Joel Lee Date: Thu, 27 Oct 2022 16:15:25 +0100 Subject: [PATCH] fix: update stray ****'s in Postgres commitfest blogpost (#9904) Update 2022-10-27-postgresql-commitfest.mdx --- apps/www/_blog/2022-10-27-postgresql-commitfest.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/www/_blog/2022-10-27-postgresql-commitfest.mdx b/apps/www/_blog/2022-10-27-postgresql-commitfest.mdx index c0c45e3785a..fdef4deb1c2 100644 --- a/apps/www/_blog/2022-10-27-postgresql-commitfest.mdx +++ b/apps/www/_blog/2022-10-27-postgresql-commitfest.mdx @@ -36,7 +36,7 @@ There are numerous benefits: Generally, all patches that touch the core code are welcome. It's not necessary that they are complex. In fact, it's an excellent strategy to start by fixing or improving something small. -The main topics to propose are \*\*\*\*bugfixes, performance, server features, clients, security, SQL commands, testing improvements, replication and recovery, procedural languages, code refactoring (yes, it's very important!), monitoring and control, and documentation. +The main topics to propose are: bugfixes, performance, server features, clients, security, SQL commands, testing improvements, replication and recovery, procedural languages, code refactoring (yes, it's very important!), monitoring and control, and documentation. Some ideas on what to submit: