Fix README.md option inconsistencies to follow two-character scheme

- Change -d to -dr in development workflow example (line 622)
- Change -h to -hp in help documentation description (line 680)
- Ensure all examples consistently use two-character options throughout documentation
- Maintain single-character options only in 'traditional approach' comparison example

README.md

@@ -619,7 +619,7 @@ sf-data-import -fl contacts.csv -so Contact -op upsert -ei Email -to MyOrg
 sf-org-create -al MyScratch -dd 7
 
 # 2. Deploy and test
-sf-deploy -to MyScratch -d "force-app/main/default/classes"
+sf-deploy -to MyScratch -dr "force-app/main/default/classes"
 sf-test-run -to MyScratch -lv RunLocalTests -cv
 
 # 3. Retrieve changes
@@ -677,7 +677,7 @@ sf-deploy -to DEMO-ORG \
 - **Automatic Environment Verification**: All wrappers auto-check SF CLI and run diagnostics when missing
 - **Consistent UX**: Arguments and output styling are aligned across Bash and PowerShell
 - **Error Handling**: Robust input validation and actionable errors
-- **Help Documentation**: Each script includes comprehensive help (-h or -Help)
+- **Help Documentation**: Each script includes comprehensive help (-hp or -Help)
 - **Flexible Input**: Supports absolute and repository-relative paths
 - **Command Echo**: Shows the actual `sf` command being executed for transparency
 - **Focused Workflows**: Deploy, validate, retrieve, test, run Apex, manage orgs, data import/export, and tail logs