Merge branch 'crawler-module' into 'master'

*.ser

*.bin

target/

.vscode/

.idea/

 No newline at end of file

The INSTALL.txt file should contain all information needed to install and run your code, from scratch, on a lab machine, including:

- Pre-conditions

  - Hardware, peripherals, and operating system restrictions for running your code ( i.e., can this code only run on lab machines, or can it run elsewhere?)

    - All code should run on our lab computers, unless you have an exemption from the instructor.

    - If some of your features work more efficiently on specific hardware, please explain this here.

- Supporting files

  - A list of non-standard libraries needed for your project to run, including:

    - Clear and simple instructions for how to freely (and legally!) acquire and install them from source code with minimal effort.

    - You may additionally link to a binary version of the libraries, if you wish.

  - Examples of how to use your project

    - Several clear examples the illustrate the main features of your project.

  - Descriptions of testing patterns, and instructions on how to exercise them:

    - unit tests

    - system tests

- Execution

  - Clear and terse instructions on how an average student in the class can compile and run all your code, from scratch, on a lab machine.

 No newline at end of file

# Group7

## Getting started

To make it easy for you to get started with GitLab, here's a list of recommended next steps.

Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!

## Add your files

- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files

- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:

```

cd existing_repo

git remote add origin https://agile.bu.edu/gitlab/ec504/ec504_projects/group7.git

git branch -M master

git push -uf origin master

```

## Integrate with your tools

- [ ] [Set up project integrations](https://agile.bu.edu/gitlab/ec504/ec504_projects/group7/-/settings/integrations)

## Collaborate with your team

- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)

- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)

- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)

- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)

- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)

## Test and Deploy

Use the built-in continuous integration in GitLab.

- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)

- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)

- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)

- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)

- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)

***

# Editing this README

When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.

## Suggestions for a good README

Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.

## Name

Choose a self-explaining name for your project.

## Description

Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.

## Badges

On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.

## Visuals

Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.

## Installation

Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.

## Usage

Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.

## Support

Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.

## Roadmap

If you have ideas for releases in the future, it is a good idea to list them in the README.

## Contributing

State if you are open to contributions and what your requirements are for accepting them.

For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.

You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.

## Authors and acknowledgment

Show your appreciation to those who have contributed to the project.

## License

For open source projects, say how it is licensed.

## Project status

If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.

## Instructions

The README.md file should contain the following information, provided in a clear, complete, self-contained, and terse manner. Do not assume that the reader has any specific familiarity with our course this semester - only a general familiarity with the course's technical content:

- Documentation

    - description of the problem

    - group members (together with any information you feel comfortable including: pictures, e-mails, etc.)

    - a high-level description of the implementation, with particular emphasis on the design decisions related to data structures and algorithms

    - a list of the features (from the project proposal) that have been implemented:

        - for each feature implemented, provide:

            - its stated value (percentage of feature grade), and

            - a description of how it was implemented with an emphasis on data structures and algorithms used.

        - if you have changed (added or removed) a feature from your [InitialProjectDefense](https://agile.bu.edu/gitlab/ec504/ec504_projects/group7/-/wikis/Initial-Project-Defense), please also provide an explanation of the change.

    - relevant references and background materials.

- Code

    - A link to the branch containing all complete, working Java 17 code used in your implementation (capable of being run on a lab machine).

    - A link to the folder containing all data needed by your project to run (ideally in your repo, or in a simple, publicly accessible location if there is too much data for our server).

    - A link to a folder containing all testing code utilized to observe the correctness of your code.

- Work breakdown

    - A detailed statement of what each member of the group contributed to the project, signed by all members of the group.

    - You may keep this private instead, if you wish, by e-mailing it directly to the instructor (trachten@bu.edu), cc'ed to the entire group.

 No newline at end of file

https://en.wikipedia.org/wiki/Web_crawler

https://link.springer.com/book/10.1007/978-3-540-46332-0

http://www.youtube.com

http://www.facebook.com

http://www.yahoo.com

http://www.amazon.com

http://www.wikipedia.org

http://www.twitter.com

http://www.live.com

http://www.bing.com

http://www.instagram.com

http://www.linkedin.com

http://www.msn.com

http://www.vk.com

http://www.hao123.com

http://www.reddit.com

http://www.ebay.com

http://www.t.co

http://www.tmall.com

http://www.sohu.com

http://www.pinterest.com

http://www.netflix.com

http://www.microsoft.com

 No newline at end of file

<?xml version="1.0" encoding="UTF-8"?>

<project xmlns="http://maven.apache.org/POM/4.0.0"

         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">

    <modelVersion>4.0.0</modelVersion>

    <groupId>edu.bu</groupId>

    <artifactId>LanguageCorrection</artifactId>

    <version>1.0-SNAPSHOT</version>

    <properties>

        <maven.compiler.source>17</maven.compiler.source>

        <maven.compiler.target>17</maven.compiler.target>

        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>

    </properties>

    <dependencies>

        <dependency>

            <groupId>org.jsoup</groupId>

            <artifactId>jsoup</artifactId>

            <version>1.15.3</version>

        </dependency>

    </dependencies>

</project>

 No newline at end of file