Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DOCS] DOC-368 spelling correction #5912

Merged
merged 1 commit into from
Sep 1, 2022

Conversation

Rachel-Reverie
Copy link
Contributor

Changes proposed in this pull request:

  • spelling correction in data assistant guide

Definition of Done

  • I have made corresponding changes to the documentation

- spelling correction
@netlify
Copy link

netlify bot commented Sep 1, 2022

Deploy Preview for niobium-lead-7998 ready!

Name Link
🔨 Latest commit 092bd06
🔍 Latest deploy log https://app.netlify.com/sites/niobium-lead-7998/deploys/6310ec2c0d61d40009368d6f
😎 Deploy Preview https://deploy-preview-5912--niobium-lead-7998.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

@github-actions github-actions bot added the devrel This item is being addressed by the Developer Relations Team label Sep 1, 2022
@Rachel-Reverie Rachel-Reverie changed the title DOC-368 spelling correction [DOCS] DOC-368 spelling correction Sep 1, 2022
@ghost
Copy link

ghost commented Sep 1, 2022

👇 Click on the image for a new way to code review
  • Make big changes easier — review code in small groups of related files

  • Know where to start — see the whole change at a glance

  • Take a code tour — explore the change with an interactive tour

  • Make comments and review — all fully sync’ed with github

    Try it now!

Review these changes using an interactive CodeSee Map

Legend

CodeSee Map Legend

Copy link
Contributor

@austiezr austiezr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! 🚀

@@ -112,7 +112,7 @@ Once you have our `SimpleCheckpoint`'s configuration defined, you can instantiat
### 6. (Optional) Edit your Expectation Suite, save, and test again.

The Onboarding Data Assistant will create as many applicable Expectations as it can for the permitted columns. This
provides a solid base for analizing your data, but may exceed your needs. It is also possible that you may possess
provides a solid base for analyzing your data, but may exceed your needs. It is also possible that you may possess
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❤️ phew

@Rachel-Reverie Rachel-Reverie enabled auto-merge (squash) September 1, 2022 17:33
@Rachel-Reverie Rachel-Reverie merged commit b0e8efd into develop Sep 1, 2022
@Rachel-Reverie Rachel-Reverie deleted the d/doc-368/spelling_correction branch September 1, 2022 17:47
Shinnnyshinshin pushed a commit that referenced this pull request Sep 1, 2022
…on-for-schema-in-spark

* develop:
  [DOCS] DOC-368 spelling correction (#5912)
Shinnnyshinshin pushed a commit that referenced this pull request Sep 1, 2022
…in-spark' into f/GREAT-465/GREAT-1204/sparkdf-execution-engine-handle-schema

* f/GREAT-465/GREAT-1204/adding-serialization-for-schema-in-spark:
  now returning data instead of empty
  [DOCS] DOC-368 spelling correction (#5912)
  [MAINTENANCE] Remove xfails from passing tests in preparation for 0.15.21 release (#5908)
  [RELEASE] 0.15.21 (#5905)
  [BUGFIX] Ensure that `DataContext.add_checkpoint()` updates existing objects in GX Cloud (#5895)
  [MAINTENANCE] `SqlAlchemyExecutionEngine` case for SQL Alchemy `Select` and `TextualSelect` due to `SADeprecationWarning` (#5902)
  [MAINTENANCE] Improve existing expectation suite unit tests (phase 1) (#5898)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
devrel This item is being addressed by the Developer Relations Team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants