-<dt>Hint application for the table which is not clarified in query </dt>
-<dd>If it matches with the name specified in Hint, then also for the tables which are appeared in view definition or query in function etc., Hint will be applicable same as in query specifying the Hint.For this, when wish to change whether to apply Hint or Hint to be applied, to their respective tables, specify different alias name. </br>
-In the following example, by specifying Alias name ‘t1’ that has been used in View definition, in SeqScan Hint, Seq Scan is selected by both table scan and scan through View. In actual table by specifying ‘t1’ that is a different alias name and which has been used in View definition, scan method can be controlled individually.
+<dt>Tables not clarified in query as that in views or in SQL functions</dt>
+<dd>Since pg_hint_plan identifies objects by the names or aliases
+ the planner sees, the names in views or quiries in SQL functions
+ appear in the target query are also valid as identifiers.
+ So, within the whole extent of the query where the planner sees
+ at once, the given name is regarded as ambiguous when it refers
+ diferrent objects in the portions implicitly included into the
+ query, say, views or SQL functions. Conversely, multiple views
+ with the same logical definition with the diferrent alias sets
+ given can be applied diferrent hints using the aliases.</br>
+In the first of the following examples, alias 't1' is refers
+both table1 in view1 and same table1 in the main query. So t1 is
+not ambiguous and SeqScan(t1) was applied to both the view and
+the main query. In the second expample, table1 in the main query
+aliased as 't3' which is different to 't1' in the view. So
+SeqScan(t3) is applied only to the table1 in main query.