11 Commits (c99f5972dee6f62eaaf96ba74ab3cd4e71d19caa)

Author	SHA1	Message	Date
Laura Pacilio	31af9adc00	Make all sentences start with caps + additional tweak wording edits	5 years ago
Laura Pacilio	a7c1ae72a4	Remove back ticks from for_each page	5 years ago
Laura Pacilio	a780f625e9	Fix metadata description format on all pages	5 years ago
Laura Pacilio	bc9065334e	Update description metadata per PR feedback	5 years ago
Laura Pacilio	f4f8d7a6c5	Change use to using for consistency with other docs	5 years ago
Laura Pacilio	96994d0b01	Add description metadata to for_each page	5 years ago
Judith Malnick	044c439dbc	Gloss of top docs pages (#28891) ... * clarify input variables opening sentence * adjust variables description * claraify providers text and add learn callout * add description to providers page * add desscription and clarify provider configuration * add deprecation note to versions in proivder configs * add hands on callout and clarify next steps in intro * link to language collection from language docs * give more context about configurtion language up front * clarify output top page * reorganize for each intro to present feature before notes * move description before link out and remove passive voice * fix typo * clarify purpose of plan * move explanation before learn link and fully spell boolean * add a syntax heading to separate intro from details * add learn callout to module source docs * clean up intro to provider requirements and add link * Apply suggestions from code review Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com> Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>	5 years ago
Martin Atkins	6f68065326	website: Explicit example of for_each chaining between resources ... This pattern follows as a natural consequence of how for_each is defined, but I've noticed from community forum Q&A that newcomers often don't immediately notice the connection between what for_each expects as input and what a for_each resource produces as a result, so my aim here is to show a short example of that in the hope of helping folks see the link here and get ideas on how to employ the technique in other situations.	5 years ago
Pam Selle	81e8167a4c	Update documentation for provider_sensitive_attrs experiment ... Update documentation to reference that this experiment is now default in 0.15+	5 years ago
Nick Fagerlund	7a8dd326c6	website: Language: Update links to moved pages	5 years ago
Nick Fagerlund	78dcc8dc1b	website: Language: Move files to match new URL structure	5 years ago