From 93334bbd65b60c130469ffc0f08f158d7d46f52f Mon Sep 17 00:00:00 2001
From: BorisTyshkevich <125603338+BorisTyshkevich@users.noreply.github.com>
Date: Fri, 20 Sep 2024 15:51:19 +0200
Subject: [PATCH] Update projections-examples.md

columns expression
---
 .../en/altinity-kb-queries-and-syntax/projections-examples.md   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/altinity-kb-queries-and-syntax/projections-examples.md b/content/en/altinity-kb-queries-and-syntax/projections-examples.md
index f4a1a4d54a..af06833691 100644
--- a/content/en/altinity-kb-queries-and-syntax/projections-examples.md
+++ b/content/en/altinity-kb-queries-and-syntax/projections-examples.md
@@ -16,7 +16,7 @@ description: >
 - Projection is used only if it is cheaper to read from it than from the table.
 - Projection should be materialized.  Verify that all parts have the needed projection by looking into the system.parts, projections column.
 - If there are many projections per table, the analyzer can select any of them. If you think that some is better use settings `preferred_optimize_projection_name` or `force_optimize_projection_name`
-- The query should use only the columns defined in the projection with the same functions and modifiers. Use column aliases to make the query the very same as in the projection definition:
+- The query should use only the columns expression (not just columns!) defined in the projection with the same functions and modifiers. Use column aliases to make the query the very same as in the projection definition:
 
 ```sql
 CREATE TABLE test