Fix a few typos

Author: Bombardier-C-Kram

README.md

@@ -2,7 +2,7 @@
 
 A C# application for parsing OpenAPI specifications and generating Dyalog APL client code.
 
-**This project is in active development and is not yet functional.**
+**This project is in active development and is not yet fully functional. Many features remain unimplemented.**
 
 ## Project Structure
 

docs/examples.md

@@ -37,7 +37,7 @@ result←api.pet.addPet.syncDetailed (client:client ⋄ Pet:newPet)
 :If result.statusCode≡200
     ⎕←'Created pet with ID: ',⍕result.parsed.id
 :Else
-    ⎕←'Error: ',result.Error
+    ⎕←'Error'
 :EndIf
 ```
 

docs/generated-code.md

@@ -58,7 +58,7 @@ The `Client.aplc` file contains the main client class that serves as the entry p
     :field public Initialised←0
 
     ∇ (rc msg)←Initialise
-      ⍝ Initialize HttpCommand
+      ⍝ ←Initialise HttpCommand
       ⍝ Checks parent namespace
     ∇
 :EndClass
@@ -95,8 +95,8 @@ Each API operation generates an individual namespace containing helper functions
     ∇
     
     ∇ r←parseResponse response
-        ⍝ Parse HTTP response based on status code
-        ⍝ HttpCommand automatically parses JSON
+        ⍝ HttpCommand returns the response body already JSON-decoded (if applicable)
+        ⍝ This function interprets that data per status code and maps it to models or errors
         ⍝ Returns: Parsed data or error information
     ∇
 :EndNamespace
@@ -152,7 +152,7 @@ Data models are generated from OpenAPI schemas:
 ### Model Features
 
 - **Type Annotations**: Comments document field types and requirements
-- **Namespace Constructor**: Accepts a namespace to initialize fields
+- **Namespace Constructor**: Accepts a namespace to initialise fields
 - **FormatNS Method**: Builds namespace for JSON serialization, excluding undefined fields
 - **Helper Functions**: `isVarDefined` checks field existence
 - **Nested Objects**: Reference types point to other model classes
@@ -174,7 +174,7 @@ The generated client surfaces errors through HTTP status codes and the `HttpComm
 - Each operation's `parseResponse` handles expected status codes
 - HttpCommand provides `HttpStatus` field for checking responses
 - Error responses are returned as-is (pre-parsed by HttpCommand)
-- Client code should check `resp.statusCode` (if using syncDetailed) to determine success/failure
+- Client code should check `result.statusCode` (if using syncDetailed) to determine success/failure
 
 ## Customization
 

docs/index.md

@@ -4,6 +4,7 @@ Welcome to the documentation for the Dyalog APL OpenAPI Client Generator. This t
 
 !!! warning "Development Status"
     This project is in active development and is not yet fully functional.
+    The documentation is also in active development, and as such many sections remain incomplete.
 
 ## Overview
 

docs/usage-guide.md

@@ -34,7 +34,7 @@ This will create a complete APL client in the `./output` directory.
 client ← ⎕NEW Client
 
 ⍝ Call an API method
-result ← api.pet.findPetsByStatus (client:client ⋄ status:'available')
+result ← api.pet.findPetsByStatus.syncDetailed (client:client ⋄ status:'available')
 
 ⍝ Handle the response
 :If result.statusCode≡200