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

WIP: Text enhancements #252

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

NehaGujar1
Copy link

What this PR does / why we need it: It is a WIP PR for text enhancements

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #251 Text enhancements in the docs

Special notes for your reviewer:

Checklist:

Copy link

netlify bot commented Feb 28, 2024

Deploy Preview for litmus-docs-411023 failed.

Name Link
🔨 Latest commit cbf1434
🔍 Latest deploy log https://app.netlify.com/sites/litmus-docs-411023/deploys/65dee03c61c19b0008a98542

Copy link

vercel bot commented Feb 28, 2024

@NehaGujar1 is attempting to deploy a commit to the Harness Chaos Team Team on Vercel.

A member of the Team first needs to authorize it.

@@ -10,26 +10,26 @@ sidebar_label: Core principles

Cloud Native Chaos Engineering, defined as engineering practices focused on (and built on) Kubernetes environments, applications, microservices, and infrastructure follows these core principles -

## Driven by Open Source
**Driven by Open Source**
Copy link
Member

Choose a reason for hiding this comment

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

Why are we removing the headings?

@@ -20,7 +20,7 @@ Kubernetes is being run on a variety of infrastructure, ranging from virtual mac

Your application resilience really depends more on the underlying stack than your application itself. It is possible that once your application is stabilized, the resilience of your service that runs on Kubernetes depends on other components and infrastructure more than 90% of the time.

Thus it is important to verify your application resilience whenever a change has happened in the underlying stack. **Keep verifying** is the key. Robust testing before upgrades is not good enough, mainly because you cannot possibly consider all sorts of faults during upgrade testing. This introduces the concept of Chaos Engineering. The process of "**continuously verifying** if your service is resilient against faults" is called Chaos Engineering.
Thus it is important to verify your application resilience whenever a change has happened in the underlying stack. **Keep verifying** is the key. Robust testing before upgrades is not good enough, mainly because you cannot possibly consider all sorts of faults during upgrade testing. This introduces the concept of Chaos Engineering. The process of "**continuously verifying if your service is resilient against faults**" is called Chaos Engineering.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
Thus it is important to verify your application resilience whenever a change has happened in the underlying stack. **Keep verifying** is the key. Robust testing before upgrades is not good enough, mainly because you cannot possibly consider all sorts of faults during upgrade testing. This introduces the concept of Chaos Engineering. The process of "**continuously verifying if your service is resilient against faults**" is called Chaos Engineering.
Thus it is important to verify your application resilience whenever a change has happened in the underlying stack. **Keep verifying** is the key. Robust testing before upgrades is not good enough, mainly because you cannot possibly consider all sorts of faults during upgrade testing. This introduces the concept of Chaos Engineering. The process of **continuously verifying if your service is resilient against faults** is called Chaos Engineering.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Text enhancements in the docs
2 participants