Apply suggestions from code review

Co-authored-by: Marek Nocoń <[email protected]>

Author: adriendupuis

docs/content_management/field_types/field_type_reference/field_type_reference.md

@@ -18,7 +18,8 @@ In addition, it's possible to extend the system by creating custom types for spe
 
     For general field type documentation, see [field type](field_types.md).
 
-Custom field types have to be programmed in PHP. However, the built-in field types are usually enough for typical scenarios.
+Custom field types have to be programmed in PHP. 
+However, the built-in field types are usually enough for typical scenarios.
 The following table gives an overview of the supported field types that come with [[= product_name =]].
 
 ## Available field types

docs/content_management/field_types/field_type_reference/imagefield.md

@@ -39,8 +39,8 @@ They're `Ibexa\Contracts\Core\Variation\Values\ImageVariation` objects with the
 
 | Property       | Type     | Example                                          | Description                                                                                                                                |
 |----------------|----------|--------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|
-| `width`*       | int      | `200`                                            | The variation's width in pixels. For more details see Caution note below.                                                                  |
-| `height`*      | int      | `112`                                            | The variation's height in pixels. For more details see Caution note below.                                                                 |
+| `width`        | int      | `200`                                            | The variation's width in pixels. For more details see Caution note below.                                                                  |
+| `height`       | int      | `112`                                            | The variation's height in pixels. For more details see Caution note below.                                                                 |
 | `name`         | string   | `medium`                                         | The variation's identifier, name of the image variation.                                                                                   |
 | `info`         | mixed    | n/a                                              | Extra information about the image, depending on the image type, such as EXIF data. If there is no information, the `info` value is `null`. |
 | `fileSize`     | int      | `31010`                                          | Size (in byte) of current variation.                                                                                                       |

docs/content_management/field_types/field_type_reference/productspecificationfield.md

@@ -6,15 +6,14 @@ month_change: true
 # Product specification field type
 
 This field represents and handles [product attributes](products.md#product-attributes) and [VAT](prices.md#vat).
-Consider it as internal to the [PIM](pim.md). 
+Consider it as internal to the [PIM](pim.md).
 
 | Name                   | Internal name                 | Expected input |
 |------------------------|-------------------------------|----------------|
 | `ProductSpecification` | `ibexa_product_specification` | mixed          |
 
 !!! caution
 
-    The presence of a specification (`ibexa_product_specification`) field is what distinct product type from content type.
+    The presence of a specification (`ibexa_product_specification`) field distincts product types from content types.
     Don't remove this field from a product type (or it becomes a unreachable hidden content type).
     Don't add such field to a content type (or it becomes an uneditable unusable product type).
-    You can't have more than one `ibexa_product_specification`, the laters won't be editable.