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] copy edits and clarify instructions to get to Jobs screenshot #154

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

angelinalg
Copy link
Contributor

Just making some copy edits for style, and clarifying instructions on how to get the Jobs screenshot.

@@ -210,19 +210,19 @@
"\n",
"**Ray dashboard > Jobs**\n",
"\n",
"To see the status of an active or previously run Ray job, navigate to `Ray Dashboard > Jobs` in the UI. Here you will see an overview of job progress, logs, and the ability to drill down into individual task and actors.\n",
"To see the status of an active or previously run Ray Job, navigate to `Ray Dashboard > Jobs` in the UI. You can see an overview of Job progress, logs, and have the ability to drill down into individual task and actors. Double-click on one of the Jobs to see a screenshot like the following:\n",
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
"To see the status of an active or previously run Ray Job, navigate to `Ray Dashboard > Jobs` in the UI. You can see an overview of Job progress, logs, and have the ability to drill down into individual task and actors. Double-click on one of the Jobs to see a screenshot like the following:\n",
"To see the status of an active or previously run Ray Job, navigate to `Ray Dashboard > Jobs` in the UI. You can see an overview of Job progress, logs, and have the ability to drill down into individual task and actors. Click on one of the Jobs to see a screenshot like the following:\n",

You don't need to double-click. Single-click is enough

@scottsun94
Copy link
Contributor

We also need to update the readme file I assume.

@ericl do we need to need to keep both readme and ipynb?

@ericl
Copy link
Contributor

ericl commented Mar 26, 2024

You can regenerate the md file using ./ci/auto-generate-readme.sh

@@ -8,17 +8,17 @@
"\n",
"**⏱️ Time to complete**: 10 min\n",
"\n",
"Welcome! You are currently in a Workspace, which is a persistent cloud IDE connected to a Ray cluster.\n",
"Welcome! You are currently in a Workspace, which is a persistent cloud IDE connected to a Ray Cluster.\n",
Copy link
Contributor

Choose a reason for hiding this comment

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

@@ -84,9 +84,9 @@
"source": [
"### Cloud Storage\n",
"\n",
"Workspace local storage is limited to 1GB, so we recommend only using it to store git repos and smaller files. To persist larger files, you can save data to cloud storage.\n",
"Because Workspace local storage is limited to 1GB, use it to store Git repos and smaller files. To persist larger files, you can save data to cloud storage.\n",
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
"Because Workspace local storage is limited to 1GB, use it to store Git repos and smaller files. To persist larger files, you can save data to cloud storage.\n",
"Because workspace local storage is limited to 1GB, use it to store Git repos and smaller files. To persist larger files, you can save data to cloud storage.\n",

I believe we are standardizing on lowercase for workspace, per previous discussions. It's only capital when introduced in the context of "Anyscale Workspace".

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.

3 participants