Skip to content

Commit bf340c0

Browse files
Remove redundant "simply" from instructions
1 parent 35be831 commit bf340c0

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/app-service/getting-started.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -46,16 +46,16 @@ Java SE on App Service allows you to effortlessly deploy your applications to fu
4646
managed Java Virtual Machine (JVM) instances. You should consider this stack if you
4747
have Spring Boot and Quarkus web applications. However, you can use this stack for any
4848
application that can be started directly from a JVM and includes an embedded
49-
HyperText Transfer Protocol (HTTP) server. You can simply deploy your
49+
HyperText Transfer Protocol (HTTP) server. You can deploy your
5050
Java archive (JAR) file and let App Service do the rest.
5151

5252
### Tomcat on App Service
5353
This App Service stack supports all recent major and minor versions of Tomcat.
5454
You should consider migrating on-premises Tomcat web applications to App Service using
5555
this stack. Such applications often use technologies such as the Spring Framework and
5656
Hibernate. The stack is also suitable for applications currently running on servers such
57-
as WebLogic or WebSphere that can be easily migrated to Tomcat. You can simply deploy
58-
your web application achive (WAR) file and let App Service do the rest.
57+
as WebLogic or WebSphere that can be easily migrated to Tomcat. You can deploy
58+
your web application archive (WAR) file and let App Service do the rest.
5959

6060
### JBoss EAP on App Service
6161
You can effortlessly run any JBoss EAP version currently supported by Red Hat on this
@@ -64,7 +64,7 @@ and Jakarta EE standards. The stack can optionally support any application that
6464
JBoss EAP clustering. You should consider migrating applications currently running
6565
on-premises on JBoss EAP and WildFly to this stack. The stack is also suitable for
6666
applications running on servers such as WebLogic or WebSphere that can be easily migrated
67-
to JBoss EAP. You can simply deploy your web application archive (WAR) or
67+
to JBoss EAP. You can deploy your web application archive (WAR) or
6868
enterprise archive (EAR) file and let App Service do the rest.
6969

7070
Use the following resources to get started with Java.

0 commit comments

Comments
 (0)