From d339dd9cac8997c5af9112abd9a9ca31b8f6267c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Adri=C3=A1n=20Chaves?= Date: Mon, 19 Jun 2023 11:26:02 +0200 Subject: [PATCH] =?UTF-8?q?rules.rst:=20item=20class=20=E2=86=92=20item=20?= =?UTF-8?q?instance?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/page-objects/rules.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/page-objects/rules.rst b/docs/page-objects/rules.rst index 1733c7c0..1a1d735a 100644 --- a/docs/page-objects/rules.rst +++ b/docs/page-objects/rules.rst @@ -10,9 +10,9 @@ URL and the requested output class (a :ref:`page object class ` or an :ref:`item class `). Rules are necessary if you want to request an item instance, because rules tell -web-poet which page object class to use to generate your item class. Rules can -also be useful as documentation or to get information about page object classes -programmatically. +web-poet which page object class to use to generate your item instance. Rules +can also be useful as documentation or to get information about page object +classes programmatically. :ref:`Rule precedence ` can also be useful. For example, to implement generic page object classes that you can override for specific