Fundamentals revision 2026

.gitignore

@@ -11,3 +11,4 @@ site/package.json
 Phils_Stuff_No_Git
 .vscode/
 sigmaquickstarts_local_dev
+CLAUDE.md

site/sigmaguides/src/Fundamentals 10: Data Modeling/fundamentals_10_data_modeling.md

@@ -456,7 +456,7 @@ The user does not see the underlying calculation, but knows that since it is a m
 ### Metric best practices:
 
 **Define Metrics in Your Data Models:**<br>
-Establish Metrics within Data Models to ensure uniform calculations across all analyses.​ When Metrics are created in Data Models (rather than on warehouse tables), users gain significantly more functionality, including a display of metrics at the top of a Data Model, and a centralized browsing UX.
+Establish Metrics within Data Models to ensure uniform calculations across all analyses. When Metrics are created in Data Models (rather than on warehouse tables), users gain significantly more functionality, including a display of metrics at the top of a Data Model, and a centralized browsing UX.
 
 **Apply Time Series to Metric Displays:**<br>
 When creating a Metric, you have the ability to specify a time series field to display the Metric value over time in all Metric previews. This provides users with more context around the KPI. You can also choose to compare metric values to previous periods if desired.
@@ -465,7 +465,7 @@ When creating a Metric, you have the ability to specify a time series field to d
 Name Metrics intuitively and provide clear descriptions to aid user understanding and adoption.​
 
 **Use Aggregations in Metrics:**<br>
-Metrics are meant to serve as aggregations over dimensional columns. They’ll always calculate at the correct level of aggregation, no matter how many groupings you use. Be sure to use aggregations in your Metric Formulas
+Metrics are meant to serve as aggregations over dimensional columns. They’ll always calculate at the correct level of aggregation, no matter how many groupings you use. Be sure to use aggregations in your Metric Formulas.
 
 ![Footer](assets/sigma_footer.png)
 <!-- END OF SECTION-->
@@ -628,7 +628,7 @@ Duration: 5
 
 Sigma data models support built-in materialization.
 
-Data models that use expensive or long-running queries, such as a complex join between data elements, or data with high cardinality, multiple grouping levels, and calculated columns, setting up materialization can enhance query performance and can help reduce compute costs.
+For data models that use expensive or long-running queries — such as complex joins between data elements, or data with high cardinality, multiple grouping levels, and calculated columns — setting up materialization can enhance query performance and reduce compute costs.
 
 Back in the data model again and in `Edit` mode, click the `+` icon next to `MATERIALIZATION` to create a new job:
 

site/sigmaguides/src/Fundamentals 3: Data_Pivot_Tables - v3/Fundamentals 3: Data_Pivot_Tables.md

@@ -114,7 +114,7 @@ Click this icon **(#3 in image below)** to display the two columns separately.
 Add `Month of Date` to the `PIVOT COLUMNS` section in the element panel.
 
 Let's adjust the `Month of Date` pivot column to `Year` by using the `DateTrunc` function:
-``` code
+```copy-code
 DateTrunc("year", [Plugs_Store_Sales/Month of Date])
 ```
 
@@ -130,7 +130,7 @@ Set the aggregation method for the `Order Number` column to `CountDistinct`:
 
 Rename these `VALUE` columns to `Total Profit` and `# Orders`.
 
-Rename the pivot table's title to `Region Sales Metrics by Year` and also change name of the `Year of Month of Date` column to `Year`.
+Rename the pivot table's title to `Region Sales Metrics by Year` and also change the name of the `Year of Month of Date` column to `Year`.
 
 Our pivot table now looks like this:
 
@@ -164,7 +164,7 @@ On the `Drill down` modal, select `Brand`:
 
 We might want to see the most recent year first. That is simple enough. 
 
-Click on the `Year` > `Year (ie: 2020)` and select sort and descending (down arrow):
+Click on the `Year` > `Year (e.g., 2020)` and select sort and descending (down arrow):
 
 <img src="assets/fpivot_9.png" width="500"/>
 
@@ -205,7 +205,7 @@ In the `Element panel` > `Format`, we can adjust the various items in the pivot
 
 In the `TABLES STYLES` section, we can easily make adjustments as shown in the image below. Note that there are separate configurations for `Header` and `Subheader` in this section:
 
-Each section will display an asterisk when the defaults have been changed::
+Each section will display an asterisk when the defaults have been changed:
 
 <img src="assets/fpivot_14.png" width="800"/>
 
@@ -228,9 +228,9 @@ Then click `Conditional formatting`:
 
 <img src="assets/fpivot_15.png" width="500"/>
 
-This opens the conditional formatting panel. We use this to create "rules" that will allow different styling effects to be applied based on the the evaluation of the rule.
+This opens the conditional formatting panel. We use this to create "rules" that will allow different styling effects to be applied based on the evaluation of the rule.
 
-For example; show all transactions where the margin in negative (sold at a loss) with a red cell background and white/bold text.
+For example; show all transactions where the margin is negative (sold at a loss) with a red cell background and white/bold text.
 
 In our case, we will configure a simple rule to drive the cell colors used in the `Total Profit` column.
 
@@ -251,7 +251,7 @@ The fill colors are already set for us; we can just use those.
 
 If we wanted to set min/max values, we would click the `Customize Domain` checkbox.
 
-Now we can see the relative profits of the product types that are making profits but the ones loosing money are still front-and-center in full red.
+Now we can see the relative profits of the product types that are making profits but the ones losing money are still front-and-center in full red.
 
 Our pivot table now looks like this:
 
@@ -261,7 +261,7 @@ Click `Publish`.
 
 There are many more features designed to improve the usability of pivot tables and to meet specific use cases.
 
-Here are just a few example that customers have found useful:
+Here are just a few examples that customers have found useful:
 
 - Empty cell display value (on/off)
 - Repeat row labels

site/sigmaguides/src/Fundamentals 4: Input - v3/Fundamentals 4: Input.md

@@ -38,7 +38,7 @@ If something is not working as you expect, here is how to [contact Sigma support
 </aside>
 
  ### Target Audience
-Typical audience for this QuickStart are users of Excel, common Business Intelligence or Reporting tools and semi-technical users who want to try out or learn Sigma. Everything is done in a browser so you already know how to use that. No SQL or technical skills are needed to do this QuickStart.
+The typical audience for this QuickStart includes users of Excel, common Business Intelligence or Reporting tools and semi-technical users who want to try out or learn Sigma. Everything is done in a browser so you already know how to use that. No SQL or technical skills are needed to do this QuickStart.
 
 ### Prerequisites
 <ul>
@@ -71,7 +71,7 @@ Sigma supports three types of input tables today:
 - Linked: Based on another workbook table, selecting only columns of interest.
 - CSV: Import data from a standard comma-delimited file. Columns are named manually or created from the CSV header.
 
-Input tables can be used as sources for tables, pivot tables, and visualizations, or incorporate data using lookups and joins. 
+Input tables can be used as sources for tables, pivot tables, and visualizations, or to incorporate data using lookups and joins. 
 
 When you create warehouse views for input tables, you can reuse the manually entered data across your broader data ecosystem.
 
@@ -133,7 +133,7 @@ Click `Create input table`.
 
 Rename the input table to `Orders_to_Approve`.
 
-Move the new input table to the `Fundamentals 4` page
+Move the new input table to the `Fundamentals 4` page.
 
 The `Fundamentals 4` page now looks like this:
 
@@ -180,7 +180,7 @@ Selecting `Order Number` > `15758` filters the input table just like it would a
 <img src="assets/finput_18.png" width="800"/>
 
 ### Tracking who made changes
-All input tables include two optional row history columns. Add these by clicking on the + icon and selecting `Last updated at` and `Last updated by`. 
+All input tables include two optional row history columns. Add these by clicking the + icon and selecting `Last updated at` and `Last updated by`. 
 
 <img src="assets/finput_12.png" width="350"/>
 
@@ -203,7 +203,7 @@ As each comment is added to a row, Sigma has saved that information automaticall
 
 At the same time, the tracking fields were updated.
 
-Input table data is maintained separately from the "original source data" -- Plugs_Store_Sales, so that the integrity of your data in the warehouse is maintained.
+Input table data is maintained separately from the "original source data" — `Plugs_Store_Sales`, so that the integrity of your data in the warehouse is maintained.
 
 No data was stored in Sigma; your data stays in your warehouse.
 
@@ -215,10 +215,10 @@ No data was stored in Sigma; your data stays in your warehouse.
 ## CSV Import
 Duration: 5
 
-It is simple to create an input table from a CSV file. Once imported, the input table can be edited directly, joined to other tables, used as source for other Sigma elements and participate in complex workflows using actions. 
+It is simple to create an input table from a CSV file. Once imported, the input table can be edited directly, joined to other tables, used as a source for other Sigma elements and participate in complex workflows using actions. 
 
 <aside class="positive">
-<strong>IMPORTANT:</strong><br>At the time of this QuickStart, CSV import supports a maximum file size of 200 MB and UTF-8 format only.
+<strong>IMPORTANT:</strong><br> At the time of this QuickStart, CSV import supports a maximum file size of 200 MB and UTF-8 format only.
 </aside>
 
 To demonstrate, we can download some sample data using this button:

site/sigmaguides/src/Fundamentals 5: Charts - v3/Fundamentals 5: Charts.md

@@ -83,7 +83,7 @@ The typical audience for this QuickStart includes users of Excel, common Busines
   <li>A computer with a current browser. It does not matter which browser you want to use.</li>
   <li>Completion of the QuickStarts Fundamentals 1 and 2</li>
   <li>Access to your Sigma environment. A Sigma trial environment is acceptable and preferred.</li>
-  <li>If have not already, you can sign up for a Sigma Trial here:</li>
+  <li>If you have not already, you can sign up for a Sigma Trial here:</li>
 </ul>
 
 <button>[Free Trial](https://www.sigmacomputing.com/free-trial/)</button>
@@ -180,7 +180,7 @@ This time, open the `Element bar` > `Charts` group and select a `Pie` chart. Dra
 
 Click `Select source`, and choose the `Plugs_Store_Sales` table from the `Data` page.
 
-Configure the pie chart as shown. Since the data has some many brands, lets assume (and filter for) the top 10 only:
+Configure the pie chart as shown. Since the data has so many brands, let's assume (and filter for) the top 10 only:
 
 <img src="assets/fcharts_9.png" width="800"/>
 
@@ -206,7 +206,7 @@ Once you know how to create one, the others will be straightforward.
 
 For example, let's say we want a `KPI` that shows `Revenue`, and compare the current month with the same month from the previous year. 
 
-Using the `Element panel`, add a new `KPI` chart, set its data source to the `Plugs_Store_Sales` table on the `Data` page
+Using the `Element panel`, add a new `KPI` chart, set its data source to the `Plugs_Store_Sales` table on the `Data` page.
 
 Now simply configure the KPI as shown below. Use the `Sales` column for `VALUE` and rename it to `Monthly Sales Trend`. Also, set a `Comparison` period:
 
@@ -246,7 +246,7 @@ One way to do this is simply use the `Monthly Sales Trend` KPI menu and select `
 
 `Order Count` is the same as the others but the formula is not `SUM` but rather `CountDistinct`.
 
-Select all four KPI at once and drag them about the charts, resizing to suit.
+Select all four KPIs at once and drag them about the charts, resizing to suit.
 
 The `Fundamentals 5` should now look similar to this:
 
@@ -275,10 +275,10 @@ Workbooks support three distinct map types: **Region**, **Point** and **Geograph
  <ul>
       <li><strong>Region: </strong>Require a single text column on the map's REGION field. For example, you can use a column “US State” to distinguish between “regions” or states in this example</li>
       <li><strong>Point: </strong>Require a number column on both the map's LATITUDE and LONGITUDE fields. For example, you may want to show store locations on a map.</li>
-      <li><strong>Geography: </strong>Support datasets with geography data (WKT format) or variant data (GeoJSON format) and are typically used to illustrate geospatial objects on a map.<li>
+      <li><strong>Geography: </strong>Support datasets with geography data (WKT format) or variant data (GeoJSON format) and are typically used to illustrate geospatial objects on a map.</li>
 </ul>
 
-Our `Plugs_Store_Sales` table has the columns we an use for `Region` and `Point` map types:
+Our `Plugs_Store_Sales` table has the columns we can use for `Region` and `Point` map types:
 
 <img src="assets/fcharts_15.png" width="800"/>
 
@@ -368,7 +368,7 @@ Some really amazing visuals can be created via plugin. For example:
 ## What we've covered
 Duration: 5
 
-In this QuickStart we learned how to use Sigma to create beautiful charts, KPIs, maps and more.
+In this QuickStart, we learned how to use Sigma to create beautiful charts, KPIs, maps and more.
 
 The next QuickStart in this series covers using [controls in Sigma](https://quickstarts.sigmacomputing.com/guide/fundamentals_6_controls_v3/index.html?index=..%2F..index#0)