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

syntax
---
 .../altinity-kb-queries-and-syntax/projections-examples.md  | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

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 f457f3a855..f4a1a4d54a 100644
--- a/content/en/altinity-kb-queries-and-syntax/projections-examples.md
+++ b/content/en/altinity-kb-queries-and-syntax/projections-examples.md
@@ -14,9 +14,9 @@ description: >
 ## Why is a projection not used?
 
 - Projection is used only if it is cheaper to read from it than from the table.
-- Projection should be materialized.  Verify that all parts need projection by looking into the system.parts`
-- If there are many projections, some other projection can be used. Force by settings `preferred_optimize_projection_name` and `force_optimize_projection_name`
-- In the projection, all fields from the query must be included. Use aliases to make the query columns the very same as in the projection definition:
+- 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:
 
 ```sql
 CREATE TABLE test