chapter 1.4.6.3.:
replace

"If we input an ascending list of numbers from 0.0 to 9.0 into the Reverse List component; the output returns a descending list from 9.0 to 0.0."

with

"If we input an ascending list of numbers from 0.0 to 50.0 into the Reverse List component; the output returns a descending list from 50.0 to 0.0."

(A And B) Or (B And C) Or (A And C)
(B and Not C) Or (C and Not B)

Both diagrams need to be corrected

in first paragraph here:

Components are the objects you place on the canvas and connect together with Wiresto form a visual program. Components can represent Rhino Geometry or operationslike Math Functions. Components have inputs and outputs.

Here's the format we should use - one # per level of depth in the outline. Use a "." after the number before the title. Let's update throughout.

Header 1

1. Foundations

Header 2

1.1. Hello Grasshopper

Header 3

1.2.3. Data Types

1. In general, leaders are crossing some of the graphics. Let's consider adjusting the protocol for labeling.
2. Gitbook rendered html isn't showing the images in the step-by-step. It works in Gitbook editor local and brackets. Do you think this will be an issue rendering on the web?

https://www.gitbook.com/content/book/gilakos/grasshopper-primer/1-foundations/f-2-2_mathematics-expressions-conditionals.html

Swap between number 6 and 7 in the description.

I found it in here:

By default, a new connection will erase existing connections. Hold the SHIFT button while dragging connection wires to difne multiple sources. The cursor will turn green to indicate the addition behavior.

It should be define I think

chapter 1.4.6.2.: to explain the picture below the text:

replace "In this example, we have set the i-input to 5.0 so the List Item component returns the data item associated with the 5th entry number in our list." with "In this example, we have set the i-input to 2 so the List Item component returns the data item associated with the 3rd entry number (index 2) in our list."

please check if my assumption is correct

chapter 1.4.4.2.
change "Total number of points = 13" to "Total number of points = 11"

Let's Use #F9F9F9 for the background and discuss the leader format.

1.3.3.5. example file link broken

Chapter 1.2.4.2.:

replace "To do this, simply click on the View Tab on the Main Menu" with "To do this, simply click on the Display Tab on the Main Menu"

I now see how Grasshopper-generated gumballs appear under different conditions than Rhino-based ones. I am going to try to improve the explanation of this in the primer.

hey good people, not sure if typos are issues but I wanted to signal that one found in:
http://grasshopperprimer.com/en/1-foundations/1-1/3_talking-to-rhino.html

it says in the first sentence of that page:

Unlike a Rhino document, a Grasshopper definition does not contain any actual objectsor geometry. Instead, a Grasshopper definition represents a set of rules & instructions for how Rhino can automate tasks.

and I guess it should be objects or geometry I could do proof reading throughout the primer if I had access to do that but I understand you might want to see theses things case by case.

Anyhow, I thought about signaling it.

I found another one here, it is in the first paragraph:

Grasshopper consists of two primary types of user objects: parameters andcomponents.

and also a little later:

(Grasshopper is to remember that we willuse data to define the inputs of actions (which will result in new data that we cancontinue to use)).

Typo, lack of space:

Attractors are points that act like virtual magnets - either attracting or repelling other objects. In Grasshopper, any geometry referenced from Rhino or created withinGrasshopper can be used as an attractor. Attractors can influence any number of parameters of surrounding objects including scale, rotation, color, and position. These parameters are changed based on their relationship to the attractor geometry.

Once I worked out all the proof reading, I'll make one pull request for all the typo issues I think.

In the Shortest List component (Trim Start), the line connecting between point 0 and 2 is missing.

it can be found here:

Draw a circle at each division point along th ecurve, normal to the tangent vector at each pont, with a radius defined by the parameter values (t) modified by the graph mapper and multiplied by 27.

it should be the curve.

In Rhino, the gumball applies to any object, and that is why I tried to do the same in Grasshopper.
In fact, the gumball widget in GH only works with points ; so I think that the wording should not be "when storing geometry...." but "when storing points..." which is more accurate and less misleading.

chapter 1.3.3.4:
delete "]]]]]]]]]]"