Skip to content

Commit 89001ec

Browse files
author
Ivy Bazan
committed
minor fix
1 parent c728bab commit 89001ec

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

doc/overview.rst

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -591,7 +591,7 @@ prebuilt model from the model zoo to train on custom data or deploy
591591
to a SageMaker endpoint for inference without signing up for
592592
SageMaker Studio.
593593

594-
The following topic give you information about Jumpstart components,
594+
The following topic give you information about JumpStart components,
595595
as well as how to use the SageMaker Python SDK for these workflows.
596596

597597
Prerequisites
@@ -608,7 +608,7 @@ Prerequisites
608608
JumpStart Components
609609
====================
610610

611-
The following sections give information about the main Jumpstart
611+
The following sections give information about the main JumpStart
612612
components and their function.
613613

614614
JumpStart models
@@ -619,7 +619,7 @@ open source datasets. You can use the SageMaker Python SDK
619619
to fine-tune a model on your own dataset or deploy it directly to a
620620
SageMaker endpoint for inference.
621621

622-
Jumpstart model artifacts are stored as tarballs in the JumpStart S3
622+
JumpStart model artifacts are stored as tarballs in the JumpStart S3
623623
bucket. Each model is versioned and contains a unique ID which can be
624624
used to retrieve the model URI. The following information describes
625625
the ``model_id`` and ``model_version`` needed to retrieve the URI.
@@ -696,14 +696,14 @@ Deploy a  Pre-Trained Model Directly to a SageMaker Endpoint
696696

697697
In this section, you learn how to take a pre-trained JumpStart model
698698
and deploy it directly to a SageMaker Endpoint. This is the fastest
699-
way to start machine learning with a Jumpstart model. The following
699+
way to start machine learning with a JumpStart model. The following
700700
assumes familiarity with `SageMaker
701701
models <https://sagemaker.readthedocs.io/en/stable/api/inference/model.html>`__
702702
and their deploy functions.
703703

704704
To begin, select a ``model_id`` and ``version`` from the JumpStart
705705
models table, as well as a model scope of either “inference” or
706-
“training”. For this example, you use a pre-trained Jumpstart model,
706+
“training”. For this example, you use a pre-trained JumpStart model,
707707
so select “inference”  for your model scope. Use the utility
708708
functions to retrieve the URI of each of the three components you
709709
need to continue.
@@ -792,7 +792,7 @@ Fine-tune a Model and Deploy to a SageMaker Endpoint
792792
====================================================
793793

794794
In this section, you initiate a training job to further train one of
795-
the pretrained Jumpstart models for your use case, then deploy it to
795+
the pretrained JumpStart models for your use case, then deploy it to
796796
a SageMaker Endpoint for inference. This lets you fine tune the model
797797
for your use case with your custom dataset. The following assumes
798798
familiarity with `SageMaker training jobs and their

0 commit comments

Comments
 (0)