diff --git a/docs/tutorial.rst b/docs/tutorial.rst index 9305b51..138a24a 100644 --- a/docs/tutorial.rst +++ b/docs/tutorial.rst @@ -86,7 +86,7 @@ A good place to start is Naming Widgets ~~~~~~~~~~~~~~ -Widgets can be given **name/ID**s so that they can be referenced by other +Widgets can be given a **name/ID** so that they can be referenced by other widgets in the blueprint. .. code-block:: @@ -301,7 +301,9 @@ Templates CSS Style Classes ----------------- -.. Unsure if to group styles with widget-specific items + +.. TODO: Unsure if to group styles with widget-specific items + Widgets can be given style classes that can be used with your CSS or `predefined styles `_ in libraries like Libadwaita. @@ -350,8 +352,8 @@ window, or pop up when you right-click some other widget. In Blueprint a ``menu`` is a ``Gio.MenuModel`` that can be shown by MenuButtons or other widgets. -In Blueprint, ``menu``s have *items*, *sections*, and *submenus*. -Like widgets, ``menu``s can also be given a **ID**. +In Blueprint, a ``menu`` can have *items*, *sections*, and *submenus*. +Like widgets, a ``menu`` can also be given an **ID**. The `Menu Model section of the Gtk.PopoverMenu documentation `_ has complete details on the menu model. @@ -413,7 +415,7 @@ or the *end* of the Headerbar. Child widgets of HeaderBars can have the *start* or *end* types. Values for child types a widget can have are defined in the widget's documentation. -Child types in blueprint are written between square brackets [] and before +Child types in blueprint are written between square brackets ``[]`` and before the child the type is for. The following blueprint code... @@ -429,6 +431,8 @@ The following blueprint code... \... would look like this: +.. code-block:: + --------------------------- | Button | --------------------------- @@ -446,6 +450,8 @@ And the following blueprint code... \... would look like this: +.. code-block:: + --------------------------- | Button | ---------------------------