jroachgolf84 opened a new issue, #71945:
URL: https://github.com/apache/airflow/issues/71945

   ### Under which category would you file this issue?
   
   Airflow Core
   
   ### Apache Airflow version
   
   main
   
   ### What happened and how to reproduce it?
   
   There are a couple of areas where the Operators documentation can be 
improved:
   
   - Handful of typos/capitalization issues (at least one under `Reserved 
params keyword`)
   - Link to pre/post-execute documentation or include enhanced docs
   
   Link to docs: 
https://airflow.apache.org/docs/apache-airflow/stable/core-concepts/operators.html
   
   ### What you think should happen instead?
   
   Typos should be corrected, enhancements made.
   
   ### Operating System
   
   _No response_
   
   ### Deployment
   
   None
   
   ### Apache Airflow Provider(s)
   
   _No response_
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Official Helm Chart version
   
   Not Applicable
   
   ### Kubernetes Version
   
   _No response_
   
   ### Helm Chart configuration
   
   _No response_
   
   ### Docker Image customizations
   
   _No response_
   
   ### Anything else?
   
   This is an issue that is reserved for the Airflow Summit "Contributors" 
Workshop. This is denoted with the label `contributors-workshop`. Out of 
respect for the organizers and participants of this workshop, **please do not 
implement a PR that addresses this issue.**
   
   If this issue is still open following Airflow Summit, the label will be 
removed and the issue can be picked up.
   
   Please show respect!
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to