Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

Some typos fixed #261

Merged
merged 1 commit into from

2 participants

@peterkokot

No description provided.

@willdurand willdurand merged commit 6e6d6fc into propelorm:master
@willdurand
Owner

thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on Nov 28, 2013
  1. @peterkokot

    typos fixed

    peterkokot authored
This page is out of date. Refresh to see the latest.
View
2  cookbook/working-with-existing-databases.markdown
@@ -44,7 +44,7 @@ $ propel reverse
4. Pay attention to any errors/warnings issued during the task execution and then examine the generated `schema.xml` file to make any corrections needed.
- 5. _'You're done! _' Now you have a `schema.xml` file in the `legacyapp/` project directory. You can now run the default Propel build to generate all the classes.
+ 5. _You're done!_ Now you have a `schema.xml` file in the `legacyapp/` project directory. You can now run the default Propel build to generate all the classes.
The generated `schema.xml` file should be used as a guide, not a final answer. There are some datatypes that Propel may not be familiar with; also some datatypes are simply not supported by Propel (e.g. arrays in PostgreSQL). Unfamiliar datatypes will be reported as warnings and substituted with a default VARCHAR datatype.
View
2  documentation/02-buildtime.markdown
@@ -169,7 +169,7 @@ Now that your database is ready, we are going to generate our model files. These
$ propel model:build
```
-Propel will generate a new `generated-classes` folder containning all the stuff you need to interact with your different tables.
+Propel will generate a new `generated-classes` folder containing all the stuff you need to interact with your different tables.
For every table in the database, Propel creates 3 PHP classes:
Something went wrong with that request. Please try again.