Restore original section order.

Author: Crell

spec.md

@@ -477,112 +477,7 @@ class ClassName
 }
 ```
 
-### 4.4 Property Hooks
-
-Object properties may also include hooks, which have a number of syntactic options.
-
-If there is only one hook implementation, and that hook implementation itself uses
-the short-hook syntax, then the hook declaration MAY be listed entirely inline.  The hook
-name MUST be separated from the opening brace and the arrow operator by a single
-space, and the semicolon ending of the hook MUST be separated from the cosing brace
-by a single space.  For example:
-
-```php
-class Example
-{
-    public string $myName { get => __CLASS__; }
-
-    public string $newName { set => ucfirst($value); }
-}
-```
-
-If those two criteria are not met, then the hook block MUST be spread across multiple lines:
-
-```php
-class Example
-{
-    public string $myName {
-        get => __CLASS__;
-    }
-
-    public string $newName {
-        set => ucfirst($value);
-    }
-}
-```
-
-When using the multi-line form, the opening brace MUST be on the same line as the property and
-the closing brace MUST be on its own line, with the body indented one level.
-
-The `=>` operator MUST have a single space on either side.
-
-If multiple hooks are declared, they MUST be separated by at least a single line break.  They
-MAY be separated by an additional blank line to aid readability.
-
-If the property includes a default value, there MUST be a single space between the default value
-and the opening brace.
-
-```php
-class Example
-{
-    public string $newName = 'Me' {
-        set => ucfirst($value);
-    }
-}
-```
-
-If a hook is using its multi-line form, the opening brace MUST be on the same line as the hook
-name, and the closing brace MUST be on its own line.  The body MUST be indented one level.
-
-```php
-class Example
-{
-    public string $newName = 'Me' {
-        set {
-            if (strlen($value) < 3) {
-                throw new \Exception('Too short');
-            }
-            $this->newName = ucfirst($value);
-        }
-    }
-}
-```
-
-For a `set` hook, if the argument name and type do not need to be redefined, then they MAY be omitted.
-
-Property hooks MAY also be defined in constructor-promoted properties.  However, they
-MUST be only a single hook, with a short-syntax body, defined on a single line as above.
-If those criteria are not met, then the promoted property MUST NOT have any hooks defined
-inline, and SHOULD instead be defined as normal property and not promoted.
-
-```php
-class Example
-{
-    public function __construct(
-        public string $name { set => ucfirst($value; }
-    ) {}
-}
-```
-
-The following is ***not allowed*** due to the hook being too complex:
-
-```php
-class Example
-{
-    public function __construct(
-        public string $name {
-            set {
-                if (strlen($value) < 3) {
-                    throw new \Exception('Too short');
-                }
-                $this->newName = ucfirst($value);
-            }
-        }
-    ) {}
-}
-```
-
-### 4.5 Methods and Functions
+### 4.4 Methods and Functions
 
 Visibility MUST be declared on all methods.
 
@@ -647,7 +542,7 @@ class Point
 }
 ```
 
-### 4.6 Method and Function Parameters
+### 4.5 Method and Function Parameters
 
 In the argument list, there MUST NOT be a space before each comma, and there
 MUST be one space after each comma.
@@ -765,7 +660,7 @@ public function process(string $algorithm, &...$parts)
 }
 ```
 
-### 4.7 Modifier Keywords
+### 4.6 Modifier Keywords
 
 Classes, properties, and methods have numerous keyword modifiers that alter how the
 engine and language handles them. When present, they MUST be in the following order:
@@ -806,7 +701,7 @@ readonly class ValueObject
 }
 ```
 
-### 4.8 Method and Function Calls
+### 4.7 Method and Function Calls
 
 When making a method or function call, there MUST NOT be a space between the
 method or function name and the opening parenthesis, there MUST NOT be a space
@@ -871,12 +766,118 @@ $someInstance
     ->run();
 ```
 
-### 4.9 Function Callable References
+### 4.8 Function Callable References
 
 A function or method may be referenced in a way that creates a closure out of it, by providing `...` in place of arguments.
 
 If so, the `...` MUST NOT include any whitespace before or after. That is, the correct format is `foo(...)`.
 
+
+### 4.9 Property Hooks
+
+Object properties may also include hooks, which have a number of syntactic options.
+
+If there is only one hook implementation, and that hook implementation itself uses
+the short-hook syntax, then the hook declaration MAY be listed entirely inline.  The hook
+name MUST be separated from the opening brace and the arrow operator by a single
+space, and the semicolon ending of the hook MUST be separated from the closing brace
+by a single space.  For example:
+
+```php
+class Example
+{
+    public string $myName { get => __CLASS__; }
+
+    public string $newName { set => ucfirst($value); }
+}
+```
+
+If those two criteria are not met, then the hook block MUST be spread across multiple lines:
+
+```php
+class Example
+{
+    public string $myName {
+        get => __CLASS__;
+    }
+
+    public string $newName {
+        set => ucfirst($value);
+    }
+}
+```
+
+When using the multi-line form, the opening brace MUST be on the same line as the property and
+the closing brace MUST be on its own line, with the body indented one level.
+
+The `=>` operator MUST have a single space on either side.
+
+If multiple hooks are declared, they MUST be separated by at least a single line break.  They
+MAY be separated by an additional blank line to aid readability.
+
+If the property includes a default value, there MUST be a single space between the default value
+and the opening brace.
+
+```php
+class Example
+{
+    public string $newName = 'Me' {
+        set => ucfirst($value);
+    }
+}
+```
+
+If a hook is using its multi-line form, the opening brace MUST be on the same line as the hook
+name, and the closing brace MUST be on its own line.  The body MUST be indented one level.
+
+```php
+class Example
+{
+    public string $newName = 'Me' {
+        set {
+            if (strlen($value) < 3) {
+                throw new \Exception('Too short');
+            }
+            $this->newName = ucfirst($value);
+        }
+    }
+}
+```
+
+For a `set` hook, if the argument name and type do not need to be redefined, then they MAY be omitted.
+
+Property hooks MAY also be defined in constructor-promoted properties.  However, they
+MUST be only a single hook, with a short-syntax body, defined on a single line as above.
+If those criteria are not met, then the promoted property MUST NOT have any hooks defined
+inline, and SHOULD instead be defined as normal property and not promoted.
+
+```php
+class Example
+{
+    public function __construct(
+        public string $name { set => ucfirst($value; }
+    ) {}
+}
+```
+
+The following is ***not allowed*** due to the hook being too complex:
+
+```php
+class Example
+{
+    public function __construct(
+        public string $name {
+            set {
+                if (strlen($value) < 3) {
+                    throw new \Exception('Too short');
+                }
+                $this->newName = ucfirst($value);
+            }
+        }
+    ) {}
+}
+```
+
 ## 5. Control Structures
 
 The general style rules for control structures are as follows: