diff --git a/doc/syntax/clause/draw.qmd b/doc/syntax/clause/draw.qmd index 5d1004d0..31bf8f3a 100644 --- a/doc/syntax/clause/draw.qmd +++ b/doc/syntax/clause/draw.qmd @@ -68,7 +68,7 @@ Remappings have to be explicit since the property name never coincide with an ae SETTING => , ... ``` -The `SETTING` clause can be used for to different things: +The `SETTING` clause can be used for two different things: * *Setting parameters*: Some layers take additional arguments that control how they behave. Often, but not always, these modify the statistical transformation in some way. An example would be the binwidth parameter in histogram which controls the width of each bin during histogram calculation. This is not a statistical property since it is not related to each record, but to the calculation as a whole. * *Setting aesthetics*: If you wish to set a specific aesthetic to a literal value, e.g. 'red' (as in the color red) then you can do so in the `SETTING` clause. Aesthetics that are set will not go through a scale but will use the provided value as-is. You cannot set an aesthetic to a column, only to a scalar literal value. diff --git a/doc/syntax/clause/label.qmd b/doc/syntax/clause/label.qmd index 1770ff6e..4e8db44d 100644 --- a/doc/syntax/clause/label.qmd +++ b/doc/syntax/clause/label.qmd @@ -2,7 +2,7 @@ title: "Define different titles with `LABEL`" --- -The `LABEL` clause is one of the simpler clauses in ggsql an allow you to override the default naming of axes and legends, as well as adding titles to the plot +The `LABEL` clause is one of the simpler clauses in ggsql and allows you to override the default naming of axes and legends, as well as adding titles to the plot. ## Clause syntax The `LABEL` clause takes one or more labeling settings. diff --git a/doc/syntax/clause/visualise.qmd b/doc/syntax/clause/visualise.qmd index aa6c12d6..b2a62ddf 100644 --- a/doc/syntax/clause/visualise.qmd +++ b/doc/syntax/clause/visualise.qmd @@ -26,7 +26,7 @@ The `mapping` can take one of three forms and all three can be mixed: * *Column name*: If you provide the name of a column in the data then the values in that column are mapped to the aesthetic or property. If the name of the column is the same as the aesthetic or property you can provide it without the following `AS ` (implicit mapping). * *Constant*: If you provide a constant like a string, number, or boolean then this value is repeated for every record in the data and mapped to the given aesthetic or property. When mapping a constant you must use the explicit form since the aesthetic/property cannot be derived. -If an asterisk is given (wildcard mapping) it indicate that every column in the layer data with a name matching a supported aesthetic or property are implicitly mapped to said aesthetic or property. If the aesthetic or property has been mapped elsewhere then that gains precedence (i.e. if writing `VISUALISE *, revenue AS y` then y will take on the data in the revenue column even if a y column exist in the data) +If an asterisk is given (wildcard mapping) it indicates that every column in the layer data with a name matching a supported aesthetic or property are implicitly mapped to said aesthetic or property. If the aesthetic or property has been mapped elsewhere then that gains precedence (i.e. if writing `VISUALISE *, revenue AS y` then y will take on the data in the revenue column even if a y column exist in the data) An `aesthetic` is a visual characteristic of what you are rendering. Different aesthetics are available depending on the layer type since e.g. linetype is not relevant for points and shape are not relevant for lines.